Kernel crash via unchecked zero segment count
Published Oct 23, 2026 · Updated Oct 23, 2026
Invalid-pointer access in the Linux MMC core allows attackers to crash the kernel via a driver-supplied zero segment count. In mmc_mq_init_request(), a truncated max_segs value reaches mmc_alloc_sg(), whose zero-size allocation returns ZERO_SIZE_PTR under SLUB; the non-null check accepts it and sg_init_table() accesses invalid memory. Triggering requires an incorrectly configured MMC host driver during request initialization; attacker control over that configuration is not established.
Summary
What happened
Invalid-pointer access in the Linux MMC core allows attackers to crash the kernel via a driver-supplied zero segment count. In mmc_mq_init_request(), a truncated max_segs value reaches mmc_alloc_sg(), whose zero-size allocation returns ZERO_SIZE_PTR under SLUB; the non-null check accepts it and sg_init_table() accesses invalid memory. Triggering requires an incorrectly configured MMC host driver during request initialization; attacker control over that configuration is not established.
The record
- CVE
- CVE-2026-98884
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 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=0 <5.15.222
- Affected versionversion=0 <6.1.189
- Affected versionversion=0 <6.12.111
- Affected versionversion=0 <6.18.53
- Affected versionversion=0 <6.6.158
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <03f5a16ec85beebabd5ab5e67ac1527f87908ded
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3e0483e93a8be320f70a1ff68d835f7f015af311
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9cca3c0c1472d6204ef8a78a6e7b3afe9610b22e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a8283f7d93f0d9336b15618b9665279ff6944319
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b037c2f7794aa01ee2a00e43c29645fd2dd2dfb9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c465608bd25d7f8565be7817a6a36a5d69f8aa14
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.
Contact us