Information Exposure Affecting kernel-64k-devel-matched package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL10-KERNEL64KDEVELMATCHED-21282996
- published21 Oct 2026
- disclosed18 Oct 2026
Introduced: 18 Oct 2026
NewCVE-2026-98711 (opens in a new tab)How to fix?
There is no fixed version for RHEL:10 kernel-64k-devel-matched.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-64k-devel-matched package and not the kernel-64k-devel-matched package as distributed by RHEL.
See How to fix? for RHEL:10 relevant fixed versions and status.
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.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2555085
- https://access.redhat.com/security/cve/CVE-2026-98711
- https://git.kernel.org/stable/c/678c8f4ba285649d5418a858d5d4f30c728a54ad
- https://git.kernel.org/stable/c/71f693a0ecccf36532dd2790f7969da6c71d5d23
- https://git.kernel.org/stable/c/7c1611780823b76219cb1478db53dfd890c4a9a2
- https://git.kernel.org/stable/c/b0e97bd40e0c2cb1a3530ef8f6250aacf3224515
- https://git.kernel.org/stable/c/b66539a4dab128fafaad736b53ce15c19d14d561