wifi: cw1200: fix TX padding OOB read leaking heap data to device
Summary
| CVE | CVE-2026-98711 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-18 16:17:24 UTC |
| Updated | 2026-10-21 13:21:39 UTC |
| Description | 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected a910e4a94f6923c8c988565525f017f687bf7205 b66539a4dab128fafaad736b53ce15c19d14d561 git |
Not specified |
| CNA |
Linux |
Linux |
affected a910e4a94f6923c8c988565525f017f687bf7205 71f693a0ecccf36532dd2790f7969da6c71d5d23 git |
Not specified |
| CNA |
Linux |
Linux |
affected a910e4a94f6923c8c988565525f017f687bf7205 b0e97bd40e0c2cb1a3530ef8f6250aacf3224515 git |
Not specified |
| CNA |
Linux |
Linux |
affected a910e4a94f6923c8c988565525f017f687bf7205 678c8f4ba285649d5418a858d5d4f30c728a54ad git |
Not specified |
| CNA |
Linux |
Linux |
affected a910e4a94f6923c8c988565525f017f687bf7205 7c1611780823b76219cb1478db53dfd890c4a9a2 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3.11 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 3.11 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.160 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.113 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.56 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.10 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/b66539a4dab128fafaad736b53ce15c19d14d561 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/b0e97bd40e0c2cb1a3530ef8f6250aacf3224515 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/71f693a0ecccf36532dd2790f7969da6c71d5d23 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/7c1611780823b76219cb1478db53dfd890c4a9a2 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/678c8f4ba285649d5418a858d5d4f30c728a54ad |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.