HIGH Introduced in 7.0
dm-integrity Superblock OOB
CVE-2026-99086
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
01Description
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.
02KernelScan AI Analysis
Risk summary
A local attacker with root privileges can modify the on-disk superblock of a suspended dm-integrity device, causing an out-of-bounds write on resume that corrupts kernel memory. This leads to privilege escalation or kernel panic. Systems using dm-integrity with privileged local users are at risk.
Vulnerability analysis
The dm-integrity driver validates the superblock when the device is first created and sizes its internal journal structures accordingly. On resume after suspend, the driver re-reads the superblock from the underlying block device to pick up runtime flags but performs no validation. An attacker with write access to the raw block device can modify geometry fields such as log2_sectors_per_block while the device is suspended. On resume, the mismatched value causes the journal index calculation to exceed the allocated journal bounds, resulting in a 512-byte write through a NULL page address. The fix snapshots the validated superblock at construction time and refuses to resume if any geometry-describing fields differ, restoring the known-good copy and returning an error.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 6.1 | 6.1.165 | 6.2 | e9ec5cbbaf4d |
| 6.12 | 6.12.75 | 6.12.117 | 0499b6d1c9d4 |
| 6.18 | 6.18.16 | 6.18.58 | 454b67fcc28c |
| 6.19 | 6.19.6 | 6.20 | — |
| 6.6 | 6.6.128 | 6.7 | fc79aeb86a2c |
| 7.2 | 7.0 | 7.2.12 | — |
| mainline | 7.0 | 7.3 | — |
| cip/6.12 | 7.0 | 6.12.117-cip35 | 0499b6d1c9d4 |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Fixed in 6.12.117-cip35 |
| cip/6.1 | Affected — no CIP fix yet (latest 6.1.190-cip62) |
| cip/6.1-rt | Affected — no CIP fix yet (latest 6.1.189-cip61-rt32) |