# CVE-2026-72100: dm-integrity: fix a bug if the bio is out of limits

> A bug in the Linux kernel dm-integrity module causes a deadlock when a bio exceeds limits, leading to a denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-72100, DEBIAN-CVE-2026-72100, GHSA-3r62-w556-w3c9, UBUNTU-CVE-2026-72100

## What is CVE-2026-72100?

CVE-2026-72100 is a high-severity vulnerability in Linux, published on 15 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

dm-integrity: fix a bug if the bio is out of limits

If dm_integrity_check_limits fails, the code would exit with
DM_MAPIO_KILL. However, the range would be already locked at this point,
and it wouldn't be unlocked, resulting in a deadlock. Let's move the
limit check up, so that when it exits, no resources are leaked.

Weakness: CWE-667 (Improper Locking)

## Which versions are affected by CVE-2026-72100?


## How do I fix CVE-2026-72100?

Apply the vendor's patch.

## Is CVE-2026-72100 being exploited?

There is no known exploitation of CVE-2026-72100 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72100 and fix it if it is affected.

What it is: CVE-2026-72100 is a high-severity vulnerability in Linux, published on 15 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72100 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72100/ (Markdown: https://insights.sbomify.com/CVE-2026-72100/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72100
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72100
- OSV: https://osv.dev/vulnerability/CVE-2026-72100

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72100/
Summaries are generated and may contain mistakes; the official description above is the record.