CVE-2026-98711wifi: cw1200: fix TX padding OOB read leaking heap data to device
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: cw1200: fix TX padding OOB read leaking heap data to device The TX path rounds the transfer size up to the bus alignment (align_size(), up to 511 bytes for SDIO, 1 byte for SPI) but sends the padded length straight from the frame buffer, which has no room reserved for the padding. cw1200_data_write() therefore reads past the end of the frame and the bus transfer carries those bytes to the device. A bogus device can collect up to 511 bytes of kernel heap data per TX frame. The RX path does not have this problem: it allocates the skb with the aligned length (alloc_len) before reading. Compute the exact padding with the bus align_size() callback, make sure queued TX frames have tailroom for it, and zero the padding bytes before the transfer so nothing past the frame is exposed. This is not expected to change driver behavior on most cases: frame contents and transfer sizes are unchanged, only the content of the padding bytes (previously undefined stale memory, now zero), which the device never reads since the WSM header carries the real frame length. The skb expansion can only fail under memory exhaustion, in which case the frame is dropped like on the existing error paths of cw1200_tx(). Discovered by Atuin - Automated Vulnerability Discovery Engine.
- CVSS
- Not yet scored
- 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 18, 2026
- First seen by InfoSec Signals
- Oct 18, 2026
Affected products
Linux Linux linux:linux (from the name) | from a910e4a94f6923c8c988565525f017f687bf7205 before 71f693a0ecccf36532dd2790f7969da6c71d5d23; from a910e4a94f6923c8c988565525f017f687bf7205 before b0e97bd40e0c2cb1a3530ef8f6250aacf3224515; from a910e4a94f6923c8c988565525f017f687bf7205 before 678c8f4ba285649d5418a858d5d4f30c728a54ad; from a910e4a94f6923c8c988565525f017f687bf7205 before 7c1611780823b76219cb1478db53dfd890c4a9a2 | CNA record |
References
- https://git.kernel.org/stable/c/71f693a0ecccf36532dd2790f7969da6c71d5d23
- https://git.kernel.org/stable/c/b0e97bd40e0c2cb1a3530ef8f6250aacf3224515
- https://git.kernel.org/stable/c/678c8f4ba285649d5418a858d5d4f30c728a54ad
- https://git.kernel.org/stable/c/7c1611780823b76219cb1478db53dfd890c4a9a2
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.