CVE-2026-80720 (GCVE-0-2026-80720)
Vulnerability from cvelistv5
Published
2026-08-28 06:53
Modified
2026-08-29 06:22
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
iomap: add a separate bio_set for iomap_split_ioend
iomap_split_ioend can split bios that already come from
iomap_ioend_bioset and thus deadlock when the bioset is exhausted.
Add a separate bio_set to avoid this deadlock.
Christian Brauner <brauner@kernel.org> says:
Mark iomap_ioend_split_bioset static as it is only used in ioend.c,
fixing the sparse warning reported by the kernel test robot.
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/iomap/ioend.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "cfc686a1174aa904dcad9b9a7c5e46b484d27e4e",
"status": "affected",
"version": "5fcbd555d48390a8c819ba7fdf55fbfcabe05c80",
"versionType": "git"
},
{
"lessThan": "4a869be56e9f6ce7462abcf324ebdefc5de051be",
"status": "affected",
"version": "5fcbd555d48390a8c819ba7fdf55fbfcabe05c80",
"versionType": "git"
},
{
"lessThan": "c679ce3be6cb63763d68ab9b5d9d73ddc0a40762",
"status": "affected",
"version": "5fcbd555d48390a8c819ba7fdf55fbfcabe05c80",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/iomap/ioend.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.15"
},
{
"lessThan": "6.15",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.44",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.8",
"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.18.44",
"versionStartIncluding": "6.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1.8",
"versionStartIncluding": "6.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "6.15",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\niomap: add a separate bio_set for iomap_split_ioend\n\niomap_split_ioend can split bios that already come from\niomap_ioend_bioset and thus deadlock when the bioset is exhausted.\n\nAdd a separate bio_set to avoid this deadlock.\n\nChristian Brauner \u003cbrauner@kernel.org\u003e says:\nMark iomap_ioend_split_bioset static as it is only used in ioend.c,\nfixing the sparse warning reported by the kernel test robot."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.5,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:N - On ZNS-backed XFS realtime volumes exported via nfsd/ksmbd, remote client write I/O reaches vfs_write()-\u003exfs_zone_alloc_and_submit()-\u003eiomap_split_ioend() in the server kernel without local shell access.\nAC:L - An attacker with write access can deterministically exhaust the 32-entry iomap_ioend_bioset via concurrent large zoned writes or direct I/O needing multiple bio_split allocations from the same pool; they control thread count and I/O size without uncontrollable races.\nPR:N - Triggering requires only permission to write realtime files on an XFS zoned filesystem via local syscall or network NFS/SMB client write; no CAP_SYS_ADMIN, ioctl, or init-namespace root is needed beyond write access to exported storage.\nUI:N - The attacker triggers the deadlock with their own concurrent write or direct-I/O requests; no separate victim must mount media, open a file, or perform any interactive action beyond the attacker\u0027s own I/O.\nS:U - The bioset mempool deadlock freezes zoned XFS I/O within the same host kernel security authority; it does not cross a VM, IOMMU, or sandbox boundary.\nC:N - This is a mempool self-deadlock with no memory corruption, out-of-bounds access, use-after-free, or information disclosure; bio_split failure returns -ENOMEM rather than leaking kernel data.\nI:N - The bug causes tasks to block indefinitely on mempool allocation but does not corrupt, modify, or overwrite file data or enable arbitrary writes or code execution.\nA:H - When iomap_ioend_bioset is exhausted, bio_split blocks on mempool_alloc() while holders cannot release entries, deadlocking writeback workers and zoned submit paths and hanging all I/O on the affected XFS zoned filesystem."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-29T06:22:35.780Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/cfc686a1174aa904dcad9b9a7c5e46b484d27e4e"
},
{
"url": "https://git.kernel.org/stable/c/4a869be56e9f6ce7462abcf324ebdefc5de051be"
},
{
"url": "https://git.kernel.org/stable/c/c679ce3be6cb63763d68ab9b5d9d73ddc0a40762"
}
],
"title": "iomap: add a separate bio_set for iomap_split_ioend",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-80720",
"datePublished": "2026-08-28T06:53:16.683Z",
"dateReserved": "2026-08-26T14:34:25.788Z",
"dateUpdated": "2026-08-29T06:22:35.780Z",
"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…