CVE-2026-72100: dm-integrity: fix a bug if the bio is out of limits
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 3d1afaa074622859678b1a1e7c1b9c0af74c89b0, 5a266764fadaff8b5c1fe37a186ebf9b09cb953e, aa5113e7155f4ea81d2c0303ab5cb272d4b32627.
Low priority for now. Upgrade to Linux Linux 3d1afaa074622859678b1a1e7c1b9c0af74c89b0, 5a266764fadaff8b5c1fe37a186ebf9b09cb953e, aa5113e7155f4ea81d2c0303ab5cb272d4b32627 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-667
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.11affected
- fb0987682c629c1d2c476f35f6fde405a5e304a4 and later · before f7989286175f32db8605e767a1a2efc62e894dc8affected · git
- fb0987682c629c1d2c476f35f6fde405a5e304a4 and later · before aa5113e7155f4ea81d2c0303ab5cb272d4b32627affected · git
- fb0987682c629c1d2c476f35f6fde405a5e304a4 and later · before 3d1afaa074622859678b1a1e7c1b9c0af74c89b0affected · git
- fb0987682c629c1d2c476f35f6fde405a5e304a4 and later · before 5a266764fadaff8b5c1fe37a186ebf9b09cb953eaffected · git
- before 6.11not affected · semver
- 6.12.97 and later · up to and including 6.12.*not affected · semver
- 6.18.40 and later · up to and including 6.18.*not affected · semver
- 7.1.5 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72098Aug 15, 2026 · dm-verity: fix buffer overflow in FEC calculation39Monitor
- ← EarlierCVE-2026-72099Aug 15, 2026 · dm-integrity: don't increment hash_offset twice28Monitor
- Later →CVE-2026-72102Aug 15, 2026 · dm_early_create: fix freeing used table on dm_resume failure31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3d1afaa074622859678b1a1e7c1b9c0af74c89b0 | Vendor (CNA) |
| Linux Linux | 5a266764fadaff8b5c1fe37a186ebf9b09cb953e | Vendor (CNA) |
| Linux Linux | aa5113e7155f4ea81d2c0303ab5cb272d4b32627 | Vendor (CNA) |
| Linux Linux | f7989286175f32db8605e767a1a2efc62e894dc8 | Vendor (CNA) |
| debian:linux | 6.12.100-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-6453419 days apartnvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path39Monitor
- CVE-2026-680855 days apartBluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled32Monitor
- CVE-2026-720120 days aparttracing/osnoise: Call synchronize_rcu() when unregistering31Monitor
- CVE-2025-68770214 days apartbnxt_en: Fix XDP_TX path30Monitor
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.