Kernel memory consumption via full-table SDIO UART probing
Published Oct 6, 2026 · Updated Oct 6, 2026
Memory leak in the Linux kernel's SDIO UART driver allows attackers to consume kernel memory via probes when all eight port slots are occupied. The sdio_uart_add_port() function allocates xmit_fifo before securing a slot in sdio_uart_table[] and returns -EBUSY without freeing that FIFO when the table is full. Repeated failures require SDIO UART device probing with a full port table; no network or unprivileged-user trigger is documented.
Summary
What happened
Memory leak in the Linux kernel's SDIO UART driver allows attackers to consume kernel memory via probes when all eight port slots are occupied. The sdio_uart_add_port() function allocates xmit_fifo before securing a slot in sdio_uart_table[] and returns -EBUSY without freeing that FIFO when the table is full. Repeated failures require SDIO UART device probing with a full port table; no network or unprivileged-user trigger is documented.
The record
- CVE
- CVE-2026-98208
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.34
- Affected versionversion=8b197a5ce7a7218bb9fc721647ba0d5734f27348 <53823e25793a97d07e6e98e0904bbf74cac8bc76
- Affected versionversion=8b197a5ce7a7218bb9fc721647ba0d5734f27348 <5e142adbbdc54afbd01fad476c91cded41d22594
- Affected versionversion=8b197a5ce7a7218bb9fc721647ba0d5734f27348 <72f4c2b7a48423c708f2c348585419a1b71ab04c
- Affected versionversion=8b197a5ce7a7218bb9fc721647ba0d5734f27348 <8a2c1bf209ba04cbd14153a771724bd5aa522fcd
- Affected versionversion=8b197a5ce7a7218bb9fc721647ba0d5734f27348 <9e992d59138fcfaa4bad7cc0750265b0a8bca100
- Affected versionversion=8b197a5ce7a7218bb9fc721647ba0d5734f27348 <ac866db277a4c73e84b4263773652e3aba326249
- Affected versionversion=8b197a5ce7a7218bb9fc721647ba0d5734f27348 <b97b5b66c93cb4aaf6358727a73fff880a774dfd
- Affected versionversion=8b197a5ce7a7218bb9fc721647ba0d5734f27348 <fd8223c53ad9553b2a349d2a40e19bbc6e60fc48
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started