Answer in brief
CVE-2026-98711 records a Unknown severity vulnerability in wifi: cw1200: fix TX padding OOB read leaking heap data to device. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 3.11 | Not reported |
| Linux/Linuxgeneric | >=a910e4a94f6923c8c988565525f017f687bf7205 <71f693a0ecccf36532dd2790f7969da6c71d5d23 || >=a910e4a94f6923c8c988565525f017f687bf7205 <b0e97bd40e0c2cb1a3530ef8f6250aacf3224515 || >=a910e4a94f6923c8c988565525f017f687bf7205 <678c8f4ba285649d5418a858d5d4f30c728a54ad || >=a910e4a94f6923c8c988565525f017f687bf7205 <7c1611780823b76219cb1478db53dfd890c4a9a2 | 71f693a0ecccf36532dd2790f7969da6c71d5d23, b0e97bd40e0c2cb1a3530ef8f6250aacf3224515, 678c8f4ba285649d5418a858d5d4f30c728a54ad, 7c1611780823b76219cb1478db53dfd890c4a9a2 |
| Linux/Linuxgeneric | >=a910e4a94f6923c8c988565525f017f687bf7205 <b66539a4dab128fafaad736b53ce15c19d14d561 || >=a910e4a94f6923c8c988565525f017f687bf7205 <71f693a0ecccf36532dd2790f7969da6c71d5d23 || >=a910e4a94f6923c8c988565525f017f687bf7205 <b0e97bd40e0c2cb1a3530ef8f6250aacf3224515 || >=a910e4a94f6923c8c988565525f017f687bf7205 <678c8f4ba285649d5418a858d5d4f30c728a54ad || >=a910e4a94f6923c8c988565525f017f687bf7205 <7c1611780823b76219cb1478db53dfd890c4a9a2 | b66539a4dab128fafaad736b53ce15c19d14d561, 71f693a0ecccf36532dd2790f7969da6c71d5d23, b0e97bd40e0c2cb1a3530ef8f6250aacf3224515, 678c8f4ba285649d5418a858d5d4f30c728a54ad, 7c1611780823b76219cb1478db53dfd890c4a9a2 |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.