Kernel crash via integrity metadata type confusion
Published Oct 18, 2026 · Updated Oct 18, 2026
Type confusion in Linux block I/O allows local users to crash the kernel via polled direct I/O with integrity metadata. In block/fops.c, iocb_bio_iopoll() passes iocb->private to bio_poll() as a bio even though metadata I/O leaves it pointing to a uio_meta. Triggering requires io_uring IOPOLL, a protection-information attribute, and access to an integrity-capable block device; the documented consequence is a kernel oops.
Summary
What happened
Type confusion in Linux block I/O allows local users to crash the kernel via polled direct I/O with integrity metadata. In block/fops.c, iocb_bio_iopoll() passes iocb->private to bio_poll() as a bio even though metadata I/O leaves it pointing to a uio_meta. Triggering requires io_uring IOPOLL, a protection-information attribute, and access to an integrity-capable block device; the documented consequence is a kernel oops.
The record
- CVE
- CVE-2026-98821
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 18, 2026CVE publishedPublication date reported by the CVE source.
- Oct 18, 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=17ecefc9fdd8c554e0d03e5a990daef19f930add
- Affected versionversion=2729a60bbfb9215997f25372ebe9b7964f038296 <2a42e6fe1293f2e2d579c9fe5bbab056dd8b880e
- Affected versionversion=2729a60bbfb9215997f25372ebe9b7964f038296 <c97ef13ad96be0e08af38dfa2ed40cded0b53e1b
- Affected versionversion=2729a60bbfb9215997f25372ebe9b7964f038296 <dd33c03cefccdfcb223e9e6262643d64f8c1ae20
- Affected versionversion=6.16.8 <6.17
- Affected versionversion=6.17
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
Public exploit references
- blktests metadata-iopoll regression reproducerproof of concept · unverified
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