CVE-2026-98711: Linux kernel · wifi: cw1200: fix TX padding OOB read leaking heap data to device
Source GCVE Database
Not known to be exploited · fixed in b66539a4dab128fafaad736b53ce15c19d14d561 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in b66539a4dab128fafaad736b53ce15c19d14d561, b0e97bd40e0c2cb1a3530ef8f6250aacf3224515, 678c8f4ba285649d5418a858d5d4f30c728a54ad +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel cw1200 driver to correctly compute and zero TX padding bytes, preventing out-of-bounds reads and data leakage. Users should apply the official kernel update containing this fix. No additional mitigation is indicated.
Description
A vulnerability in the Linux kernel's cw1200 WiFi driver allowed out-of-bounds reads during TX padding, leaking up to 511 bytes of kernel heap data to the device. The issue was caused by reading beyond the frame buffer when padding the transfer size for bus alignment. The vulnerability has been resolved by correctly computing padding, ensuring sufficient tailroom, and zeroing padding bytes before transfer.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98711 (opens in a new tab)
- git.kernel.org/stable/c/678c8f4ba285649d5418a858d5d4f30c728a54ad (opens in a new tab)
- git.kernel.org/stable/c/71f693a0ecccf36532dd2790f7969da6c71d5d23 (opens in a new tab)
- git.kernel.org/stable/c/7c1611780823b76219cb1478db53dfd890c4a9a2 (opens in a new tab)
- git.kernel.org/stable/c/b0e97bd40e0c2cb1a3530ef8f6250aacf3224515 (opens in a new tab)