Cloudanix VulnDB

CVE-2025-68360

None

CVSS

—

EPSS

0.5%

Published

Dec 24, 2025

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A bug in the Linux kernel's handling of certain WiFi hardware can cause computers or routers to suddenly crash when processing network traffic on specific setups.

Exploitation
Local Privilege
Attacker needs
Local User
Complexity
Moderate
Impact
Denial Of Service
Component
OS kernel
Class
Memory Corruption
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Incorrect reference to primary wed device instead of wed_hif2 in mt76 driver callbacks causes invalid memory dereference (kernel read from unreadable address) during IPv6 flow offload operations, resulting in Oops and system crash.

Why it matters to the business

Systems running affected MediaTek WiFi hardware in dual-wed configurations experience unexpected kernel panics and reboots during normal network traffic handling, causing operational downtime; prevalence in Linux kernel trees increases exposure across embedded and router deployments.

How an attack unfolds

The flaw is triggered during legitimate nf_flow_table operations on systems using wed_hif2 (e.g., 6 GHz links); an attacker or automated process initiates IPv6 flow offload to reach mt76_wed_offload_disable with the wrong wed pointer, leading to a crash. No known threat actor campaigns or ransomware usage; low EPSS indicates minimal active exploitation.

How to fix it

Apply the upstream fix from commit ab94ecb997fd1bbc501a0116c7aad51556b67c86; update to fixed kernel versions or packages such as flux-image-reflector-controller-fips 0.34.0-r1; rebuild and deploy patched kernels to affected devices before the general remediation expectations for similar kernel issues.

How to confirm the fix worked

Verify kernel source contains the corrected wed reference selection logic; test on hardware with wed_hif2 enabled by exercising nf_flow_table IPv6 paths and confirm absence of the described Oops; check git history for ab94ecb997fd1bbc501a0116c7aad51556b67c86.

Typical attack path

  1. Identify or configure target with MT7996 hardware running wed_hif2 offload
  2. Initiate IPv6 network flow that engages nf_flow_offload_ipv6_hook
  3. Trigger mtk_wed_flow_remove path that calls mt76_wed_offload_disable with incorrect wed reference
  4. Cause kernel read fault at invalid address resulting in panic

How to detect it

Search kernel logs, dmesg, and system crash reports for traces containing mt76_wed_offload_disable, mtk_wed_flow_remove, and nf_flow_rule_route_ipv6; look for Mem abort info with ESR 0x0000000096000005 and invalid address 000000000000080a on systems with MT7996 hardware.

  • mt76_wed_offload_disable+0x64/0xa0 [mt76]
  • mtk_wed_flow_remove+0x58/0x80
  • Unable to handle kernel read from unreadable memory at virtual address 000000000000080a
  • ESR = 0x0000000096000005
  • nf_flow_rule_route_ipv6 [nf_flow_table]

What your security team should do

  • Immediately identify and patch all systems using mt76 driver with wed_hif2 configurations
  • Monitor kernel logs for oops involving mt76_wed_offload_disable until patches are deployed
  • Prioritize updates on high-availability routers and embedded devices given 306 days since publication
  • Test patched kernels in lab environments replicating 6 GHz link scenarios before production rollout

The record

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks MT7996 driver can use both wed and wed_hif2 devices to offload traffic from/to the wireless NIC. In the current codebase we assume to always use the primary wed device in wed callbacks resulting in the following crash if the hw runs wed_hif2 (e.g. 6GHz link). [ 297.455876] Unable to handle kernel read from unreadable memory at virtual address 000000000000080a [ 297.464928] Mem abort info: [ 297.467722] ESR = 0x0000000096000005 [ 297.471461] EC = 0x25: DABT (current EL), IL = 32 bits [ 297.476766] SET = 0, FnV = 0 [ 297.479809] EA = 0, S1PTW = 0 [ 297.482940] FSC = 0x05: level 1 translation fault [ 297.487809] Data abort info: [ 297.490679] ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 [ 297.496156] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 297.501196] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 297.506500] user pgtable: 4k pages, 39-bit VAs, pgdp=0000000107480000 [ 297.512927] [000000000000080a] pgd=08000001097fb003, p4d=08000001097fb003, pud=08000001097fb003, pmd=0000000000000000 [ 297.523532] Internal error: Oops: 0000000096000005 [#1] SMP [ 297.715393] CPU: 2 UID: 0 PID: 45 Comm: kworker/u16:2 Tainted: G O 6.12.50 #0 [ 297.723908] Tainted: [O]=OOT_MODULE [ 297.727384] Hardware name: Banana Pi BPI-R4 (2x SFP+) (DT) [ 297.732857] Workqueue: nf_ft_offload_del nf_flow_rule_route_ipv6 [nf_flow_table] [ 297.740254] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 297.747205] pc : mt76_wed_offload_disable+0x64/0xa0 [mt76] [ 297.752688] lr : mtk_wed_flow_remove+0x58/0x80 [ 297.757126] sp : ffffffc080fe3ae0 [ 297.760430] x29: ffffffc080fe3ae0 x28: ffffffc080fe3be0 x27: 00000000deadbef7 [ 297.767557] x26: ffffff80c5ebca00 x25: 0000000000000001 x24: ffffff80c85f4c00 [ 297.774683] x23: ffffff80c1875b78 x22: ffffffc080d42cd0 x21: ffffffc080660018 [ 297.781809] x20: ffffff80c6a076d0 x19: ffffff80c6a043c8 x18: 0000000000000000 [ 297.788935] x17: 0000000000000000 x16: 0000000000000001 x15: 0000000000000000 [ 297.796060] x14: 0000000000000019 x13: ffffff80c0ad8ec0 x12: 00000000fa83b2da [ 297.803185] x11: ffffff80c02700c0 x10: ffffff80c0ad8ec0 x9 : ffffff81fef96200 [ 297.810311] x8 : ffffff80c02700c0 x7 : ffffff80c02700d0 x6 : 0000000000000002 [ 297.817435] x5 : 0000000000000400 x4 : 0000000000000000 x3 : 0000000000000000 [ 297.824561] x2 : 0000000000000001 x1 : 0000000000000800 x0 : ffffff80c6a063c8 [ 297.831686] Call trace: [ 297.834123] mt76_wed_offload_disable+0x64/0xa0 [mt76] [ 297.839254] mtk_wed_flow_remove+0x58/0x80 [ 297.843342] mtk_flow_offload_cmd+0x434/0x574 [ 297.847689] mtk_wed_setup_tc_block_cb+0x30/0x40 [ 297.852295] nf_flow_offload_ipv6_hook+0x7f4/0x964 [nf_flow_table] [ 297.858466] nf_flow_rule_route_ipv6+0x438/0x4a4 [nf_flow_table] [ 297.864463] process_one_work+0x174/0x300 [ 297.868465] worker_thread+0x278/0x430 [ 297.872204] kthread+0xd8/0xdc [ 297.875251] ret_from_fork+0x10/0x20 [ 297.878820] Code: 928b5ae0 8b000273 91400a60 f943fa61 (79401421) [ 297.884901] ---[ end trace 0000000000000000 ]--- Fix the issue detecting the proper wed reference to use running wed callabacks.

Affected packages

Ecosystem Package Introduced Fixed
Linux Kernel 6.8.0 6.17.13
openSUSE:Leap 16.0 dtb-aarch64 0 6.12.0-160000.26.1
openSUSE:Leap 16.0 kernel-64kb 0 6.12.0-160000.26.1
openSUSE:Leap 16.0 kernel-azure 0 6.12.0-160000.26.1
openSUSE:Leap 16.0 kernel-default 0 6.12.0-160000.26.1
openSUSE:Leap 16.0 kernel-default-base 0 6.12.0-160000.26.1.160000.2.7
openSUSE:Leap 16.0 kernel-docs 0 6.12.0-160000.26.1
openSUSE:Leap 16.0 kernel-kvmsmall 0 6.12.0-160000.26.1
openSUSE:Leap 16.0 kernel-obs-build 0 6.12.0-160000.26.1
openSUSE:Leap 16.0 kernel-obs-qa 0 6.12.0-160000.26.1
openSUSE:Leap 16.0 kernel-rt 0 6.12.0-160000.26.1
openSUSE:Leap 16.0 kernel-source 0 6.12.0-160000.26.1
openSUSE:Leap 16.0 kernel-syms 0 6.12.0-160000.26.1
openSUSE:Leap 16.0 kernel-zfcpdump 0 6.12.0-160000.26.1
openSUSE:Tumbleweed kernel-source 0 6.18.5-1.1
openSUSE:Tumbleweed kernel-source-longterm 0 6.18.16-1.1

Related vulnerabilities