CVE-2026-99086: dm-integrity: validate the superblock on resume
In the Linux kernel, the following vulnerability has been resolved:
dm-integrity: validate the superblock on resume
dmintegrityresume() 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, accessjournaldata() shifts the journal entry index by ic->sb->log2sectorsperblock, while ic->journalsectionsectors and the journal page list were computed with the value that was present at constructor time. Increasing log2sectorsperblock makes the index run past the end of the journal, and dm-integrity then writes 512 bytes through lowmempageaddress(NULL).
Snapshot the validated superblock in the constructor and refuse to resume if any of the fields that describe the on-disk geometry changed.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.117-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.12-1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.3.0-10.10 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.3.0-1004.5 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.3.0-10.10.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.3.0-10.10.1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.2 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.7 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.117 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.58 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.20 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.12 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.117-1Fixed in 7.3.4-1 - Compensating control
Snapshot the validated superblock in the constructor and refuse to resume if any on-disk geometry fields have changed.
Event History
Frequently Asked Questions
What conditions are required to trigger this issue?
A dm-integrity device must be suspended, and the superblock on its underlying device must be modified before the device is resumed. The changed geometry must disagree with the values used when dm-integrity constructed its in-memory journal structures.
What type of superblock change is especially dangerous?
Increasing log2_sectors_per_block can cause dm-integrity to calculate a journal index beyond the end of the journal. This can lead to a 512-byte write through lowmem_page_address(NULL).
How does the resolved implementation prevent the problem?
It snapshots the validated superblock during construction and refuses to resume the dm-integrity device if fields describing on-disk geometry have changed.