CVE-2026-98711 json
wifi: cw1200: fix TX padding OOB read leaking heap data to device
published 24d ago modified 12d ago also EUVD-2026-103965
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.10-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98711
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-43.43
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1017.18
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1017.19
- linux-gke Ubuntu 24.04 LTS 6.8.0-1068.77
- linux-gke Ubuntu 26.04 LTS 7.0.0-1010.11
ubuntu advisories UBUNTU-CVE-2026-98711
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default Linux Micro 6.0 6.4.0-159998.55.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default-base Linux Micro 6.0 6.4.0-159998.55.1.159998.21.42
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.90.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.90.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
suse advisories SUSE-SU-2026:24550-1SUSE-SU-2026:5091-1
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-108893
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/8e8e4d0b15f174d964a48b1c54dc8828e5ae87c5 commit
- git.kernel.org/stable/c/a7eae7547ae1443bfbca2cb90d3ef5e501d6445c commit
- git.kernel.org/stable/c/5897945635aa5413595bf696127493be96c08e2d commit
- git.kernel.org/stable/c/b66539a4dab128fafaad736b53ce15c19d14d561 commit
- git.kernel.org/stable/c/71f693a0ecccf36532dd2790f7969da6c71d5d23 commit
- git.kernel.org/stable/c/b0e97bd40e0c2cb1a3530ef8f6250aacf3224515 commit
- git.kernel.org/stable/c/678c8f4ba285649d5418a858d5d4f30c728a54ad commit
- git.kernel.org/stable/c/7c1611780823b76219cb1478db53dfd890c4a9a2 commit
Is CVE-2026-98711 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98711 updated cvss 4.6
kernel: kernel: cw1200: Information disclosure via out-of-bounds read during frame transmission
-
Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/8e8e4d0b15f174d964a48b1c54dc8828e5ae87c5
- git.kernel.org /stable/c/a7eae7547ae1443bfbca2cb90d3ef5e501d6445c
- git.kernel.org /stable/c/5897945635aa5413595bf696127493be96c08e2d
- git.kernel.org /stable/c/b66539a4dab128fafaad736b53ce15c19d14d561
- git.kernel.org /stable/c/71f693a0ecccf36532dd2790f7969da6c71d5d23
- git.kernel.org /stable/c/b0e97bd40e0c2cb1a3530ef8f6250aacf3224515
- git.kernel.org /stable/c/678c8f4ba285649d5418a858d5d4f30c728a54ad
- git.kernel.org /stable/c/7c1611780823b76219cb1478db53dfd890c4a9a2
Sources
- CVE List CVE-2026-98711
- NVD CVE-2026-98711
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.