A bug in the dm-integrity subsystem of the Linux kernel caused resources to be locked when a limit check failed. The failure path exited with DM_MAPIO_KILL, but the range lock was already held and never released, producing a deadlock that can freeze the kernel or block operations. This condition results in a denial‑of‑service where the system may become unresponsive, and the likely attack vector is a local privileged user able to exercise block device operations that trigger an out‑of‑bounds bio. The impact is observable as a system hang, low availability, and possible stale lock data.

The flaw affects the dm-integrity module in the Linux kernel across all releases that do not include the patch fix. Vendor name is Linux, product is the Linux kernel, version information is not specified in the advisory, so all current kernel versions prior to the fix are considered vulnerable.

The CVSS score is 8.8, and the EPSS score is < 1%, indicating a high‑severity risk with low current exploitation probability. The vulnerability is not listed in the CISA KEV catalog, indicating no publicly known exploits yet. However, the resource leak can be exploited by a local attacker with sufficient privileges to instruct the kernel to operate on an out‑of‑bounds block device request, leading to a kernel deadlock. The condition is a high‑severity local denial‑of‑service that could be mitigated by applying a security patch or by disabling the affected module.