CVE-2026-99086
dm-integrity: validate the superblock on resume
No known exploitation. No EPSS score yet. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 38625191f32f77a9d5fc7cc15f4f9b78768bfb33, < 454b67fcc28c18502e47dfb9f067b04c28628adaUpgrade to: 454b67fcc28c18502e47dfb9f067b04c28628adaAffected: ≥ 118ba36e446c01e3cd34b3eedabf1d9436525e1d, < e9ec5cbbaf4dd3a02ae3d81719f4fcb9b609aa8eUpgrade to: e9ec5cbbaf4dd3a02ae3d81719f4fcb9b609aa8eAffected: ≥ 118ba36e446c01e3cd34b3eedabf1d9436525e1d, < fc79aeb86a2c244c1f1894e2d8f2966fe2b60fa2Upgrade to: fc79aeb86a2c244c1f1894e2d8f2966fe2b60fa2Affected: 824b9c27d7b600520b95f0cab95a47d1b08a9483Upgrade to: not stated + 8 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: dm-integrity: validate the superblock on resume dm_integrity_resume() re-reads the superblock from the device so that it picks up the flags and the recalculate position. It performs no validation on the result, while the constructor validates the superblock it reads and sizes all the in-memory structures according to it. The user may modify the superblock on the underlying device while the dm-integrity device is suspended, so that the two no longer agree. In particular, access_journal_data() shifts the journal entry index by ic->sb->log2_sectors_per_block, while ic->journal_section_sectors and the journal page list were computed with the value that was present at constructor time. Increasing log2_sectors_per_block makes the index run past the end of the journal, and dm-integrity then writes 512 bytes through lowmem_page_address(NULL). Snapshot the validated superblock in the constructor and refuse to resume if any of the fields that describe the on-disk geometry changed.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
No EPSS score yet. New CVEs are usually scored within a few days.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI