CVE-2026-72100 (GCVE-0-2026-72100)
Vulnerability from cvelistv5
Published
2026-08-15 05:52
Modified
2026-08-17 05:40
Severity ?
VLAI Severity ?
EPSS score ?
Summary
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.
References
| URL | Tags | |
|---|---|---|
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/md/dm-integrity.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "f7989286175f32db8605e767a1a2efc62e894dc8",
"status": "affected",
"version": "fb0987682c629c1d2c476f35f6fde405a5e304a4",
"versionType": "git"
},
{
"lessThan": "aa5113e7155f4ea81d2c0303ab5cb272d4b32627",
"status": "affected",
"version": "fb0987682c629c1d2c476f35f6fde405a5e304a4",
"versionType": "git"
},
{
"lessThan": "3d1afaa074622859678b1a1e7c1b9c0af74c89b0",
"status": "affected",
"version": "fb0987682c629c1d2c476f35f6fde405a5e304a4",
"versionType": "git"
},
{
"lessThan": "5a266764fadaff8b5c1fe37a186ebf9b09cb953e",
"status": "affected",
"version": "fb0987682c629c1d2c476f35f6fde405a5e304a4",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/md/dm-integrity.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.11"
},
{
"lessThan": "6.11",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.97",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.40",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.97",
"versionStartIncluding": "6.11",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.40",
"versionStartIncluding": "6.11",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1.5",
"versionStartIncluding": "6.11",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "6.11",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm-integrity: fix a bug if the bio is out of limits\n\nIf dm_integrity_check_limits fails, the code would exit with\nDM_MAPIO_KILL. However, the range would be already locked at this point,\nand it wouldn\u0027t be unlocked, resulting in a deadlock. Let\u0027s move the\nlimit check up, so that when it exits, no resources are leaked."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 8.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:N - The bug is hit in dm_integrity_map_inline() on block I/O to dm-integrity inline volumes; in enterprise/cloud deployments those volumes are commonly exported over network block protocols (iSCSI, NVMe-oF, NBD), letting a remote initiator drive the vulnerable map path.\nAC:L - During SB_FLAG_RECALCULATING the attacker can reliably issue concurrent I/O ahead of the recalc cursor that fails dm_integrity_check_limits (e.g., block-aligned totals with misaligned bvecs), acquiring integrity_range_locked before DM_MAPIO_KILL without cleanup.\nPR:L - Exploitation requires submitting crafted block I/O to the dm-integrity device\u2014available to unprivileged users with device access (disk group), CAP_SYS_ADMIN in a user namespace that can create dm targets, or authenticated remote block-storage clients\u2014not fully unauthenticated network access.\nUI:N - Triggering the flaw needs only attacker-initiated block I/O during recalculation; no victim interaction such as opening files or mounting filesystems is required.\nS:U - Impact is kernel heap corruption, deadlock, and privilege escalation within the host kernel security domain; it does not cross a VM/hypervisor or IOMMU boundary.\nC:H - On DM_MAPIO_KILL the dm core frees the bio/per-io dm_integrity_io while dio-\u003erange remains in ic-\u003ein_progress, creating a use-after-free that can be leveraged for arbitrary kernel memory disclosure via subsequent tree walks.\nI:H - The dangling dm_integrity_range node in the red-black tree enables heap metadata corruption and attacker-controlled reuse of freed dm_integrity_io memory, supporting arbitrary kernel write and local privilege escalation.\nA:H - The leaked range lock permanently blocks overlapping I/O (uninterruptible waits/deadlock), and UAF on in_progress tree operations can cause kernel oops/panic, producing severe and persistent loss of availability."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-17T05:40:15.688Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/f7989286175f32db8605e767a1a2efc62e894dc8"
},
{
"url": "https://git.kernel.org/stable/c/aa5113e7155f4ea81d2c0303ab5cb272d4b32627"
},
{
"url": "https://git.kernel.org/stable/c/3d1afaa074622859678b1a1e7c1b9c0af74c89b0"
},
{
"url": "https://git.kernel.org/stable/c/5a266764fadaff8b5c1fe37a186ebf9b09cb953e"
}
],
"title": "dm-integrity: fix a bug if the bio is out of limits",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-72100",
"datePublished": "2026-08-15T05:52:44.923Z",
"dateReserved": "2026-08-09T03:40:39.905Z",
"dateUpdated": "2026-08-17T05:40:15.688Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…