Kernel crash via unchecked superblock reload
Published Oct 23, 2026 · Updated Oct 23, 2026
Memory corruption in Linux dm-integrity allows local users to crash the kernel via a modified on-disk superblock. dm_integrity_resume() reloads geometry without checking it against the constructor's allocations, so increasing log2_sectors_per_block drives access_journal_data() beyond its journal pages and into a NULL-pointer write. Triggering requires write access to the backing superblock while the target is suspended, followed by resume and journal activity; code execution is not established.
Summary
What happened
Memory corruption in Linux dm-integrity allows local users to crash the kernel via a modified on-disk superblock. dm_integrity_resume() reloads geometry without checking it against the constructor's allocations, so increasing log2_sectors_per_block drives access_journal_data() beyond its journal pages and into a NULL-pointer write. Triggering requires write access to the backing superblock while the target is suspended, followed by resume and journal activity; code execution is not established.
The record
- CVE
- CVE-2026-99086
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- 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=118ba36e446c01e3cd34b3eedabf1d9436525e1d <e9ec5cbbaf4dd3a02ae3d81719f4fcb9b609aa8e
- Affected versionversion=118ba36e446c01e3cd34b3eedabf1d9436525e1d <fc79aeb86a2c244c1f1894e2d8f2966fe2b60fa2
- Affected versionversion=38625191f32f77a9d5fc7cc15f4f9b78768bfb33 <454b67fcc28c18502e47dfb9f067b04c28628ada
- Affected versionversion=3ff70e2e31c419e2230d0c66cb2bfb3b1b414b7f
- Affected versionversion=6.1.165 <6.2
- Affected versionversion=6.12.75 <6.13
- Affected versionversion=6.18.16 <6.18.58
- Affected versionversion=6.19.6 <6.20
- Affected versionversion=6.6.128 <6.7
- Affected versionversion=7.0
- Affected versionversion=824b9c27d7b600520b95f0cab95a47d1b08a9483
- Affected versionversion=c6138af1f5454c2631a837916fda958ea72c0d71
- Affected versionversion=fb49f209995f729053c6ee728436f98d78a49b6f
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
- syzbot dm-integrity superblock C 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.
Contact us