CVE-2026-80944wifi: mwifiex: Detach sync cmd buffer on interrupted wait
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Detach sync cmd buffer on interrupted wait mwifiex synchronous commands keep the caller-provided data buffer in cmd_node->data_buf. Several callers pass stack-allocated objects there. If wait_event_interruptible_timeout() is interrupted, the caller can return and release that stack object while the firmware command is still the current command. A late firmware response then reaches the normal response handler, which can copy data through cmd_node->data_buf into the stale stack address. This fixes a stack corruption observed during repeated association and disassociation cycles. The panic trace showed the command wait being interrupted immediately before a bad pointer dereference: cmd_wait_q terminated: -512 Unable to handle kernel paging request at virtual address 002c583837384662 Kernel panic - not syncing: stack-protector: Kernel stack is corrupted ... Tainted: [M]=MACHINE_CHECK The fault address decodes as little-endian ASCII: 0x002c583837384662 -> "bF878X,\0" which is a fragment of the VERSION_EXT firmware string exposed as debugfs "verext": w8997o-V4, RF878X, FP92, 16.92.21.p153.7 The same runs also showed corrupted control data containing: 0x2400372e333531 -> "153.7\0$" which is the tail of the same VERSION_EXT string. This points at a late VERSION_EXT response writing through a stale stack-backed data_buf after the interrupted wait returned. After cancelling pending commands on an interrupted or timed-out wait, detach the caller-owned data buffer from the still-current command. This preserves the existing command cancellation behaviour while preventing a late response from writing through a pointer whose lifetime ended with the waiting caller. Tested on an i.MX8MP board using an 88W8997.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 3d026d09b28dda24777129a931634949c75a9181 before 8c67b8c50286e0cb7f18d667e6a37a2ec6e08ff9; from 3d026d09b28dda24777129a931634949c75a9181 before 9024c7729eb523cf4f3a4203966d3a4aaabf030d; from 3d026d09b28dda24777129a931634949c75a9181 before 9e06c9c8a1f10c55d9bc5d139656d58795e64483; from 3d026d09b28dda24777129a931634949c75a9181 before f2134d6ff30cd6e1bf63d6b0a5d8e0839f0168b3; from 3d026d09b28dda24777129a931634949c75a9181 before 20ee9c03f261bf6ac59331e2ca7b46b23646412a; from 3d026d09b28dda24777129a931634949c75a9181 before b1bbeb8970eeb6c6bf3cd5314138103f7b69446d; from 3d026d09b28dda24777129a931634949c75a9181 before d29a165588b6a0cf7a38db5cbd602aef7ef8c658; from 3d026d09b28dda24777129a931634949c75a9181 before ef06882c7d8a7400b67d0d003b1008093dd589ed | CNA record |
References
- https://git.kernel.org/stable/c/8c67b8c50286e0cb7f18d667e6a37a2ec6e08ff9
- https://git.kernel.org/stable/c/9024c7729eb523cf4f3a4203966d3a4aaabf030d
- https://git.kernel.org/stable/c/9e06c9c8a1f10c55d9bc5d139656d58795e64483
- https://git.kernel.org/stable/c/f2134d6ff30cd6e1bf63d6b0a5d8e0839f0168b3
- https://git.kernel.org/stable/c/20ee9c03f261bf6ac59331e2ca7b46b23646412a
- https://git.kernel.org/stable/c/b1bbeb8970eeb6c6bf3cd5314138103f7b69446d
- https://git.kernel.org/stable/c/d29a165588b6a0cf7a38db5cbd602aef7ef8c658
- https://git.kernel.org/stable/c/ef06882c7d8a7400b67d0d003b1008093dd589ed
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.