Impact
An omission in the dm-integrity subsystem causes the kernel to re‑read a superblock after resumption without verifying its integrity. If the on‑disk geometry has been altered while the device was suspended, the kernel miscalculates journal offsets, writes beyond an intended memory boundary, and corrupts kernel memory. The resulting corruption can be leveraged to gain kernel privileges.
Affected Systems
All Linux kernel builds that compile dm-integrity and have not incorporated commit 454b67fcc28c18502e47dfb9f067b04c28628ada are affected. This includes mainstream releases and custom kernels that omit the added superblock validation. Devices using any dm‑integrity target on removable or non‑volatile storage are vulnerable when the integrity module is suspended.
Risk and Exploitability
The CVSS score of 4.4 indicates a moderate severity, while the EPSS score of less than 1% reflects a low probability of public exploitation. The vulnerability requires local or administrative access to the block device to modify the superblock, making the attack vector local. Successful exploitation would overwrite kernel memory and could result in a system crash or privilege escalation. Although not listed in the CISA KEV catalog, the potential for kernel corruption warrants prompt attention.
OpenCVE Enrichment