CVE-2026-72100
Linux dm-integrity bug can deadlock block I/O, causing storage/system DoS.
Is CVE-2026-72100 being exploited?
Not confirmed. CVE-2026-72100 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.56% probability of exploitation in the next 30 days.
How severe is CVE-2026-72100?
CVE-2026-72100 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-72100?
Yes. A fix has been recorded for CVE-2026-72100. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72100 affect?
CVE-2026-72100 affects Linux kernel (dm-integrity), Device-mapper integrity target, Distributions with vulnerable kernel/device-mapper enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72100?
Apply vendor kernel patches and reboot affected hosts immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Deadlock of device-mapper integrity ranges causing storage hang or system DoS; triggered by crafted block I/O to dm-integrity volumes.
Patch when possible
- affected>= fb0987682c629c1d2c476f35f6fde405a5e304a4 and < f7989286175f32db8605e767a1a2efc62e894dc8
- affected>= fb0987682c629c1d2c476f35f6fde405a5e304a4 and < aa5113e7155f4ea81d2c0303ab5cb272d4b32627
- affected>= fb0987682c629c1d2c476f35f6fde405a5e304a4 and < 3d1afaa074622859678b1a1e7c1b9c0af74c89b0
- affected>= fb0987682c629c1d2c476f35f6fde405a5e304a4 and < 5a266764fadaff8b5c1fe37a186ebf9b09cb953e
- affected6.11
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.