CVE-2026-72367 (GCVE-0-2026-72367)
Vulnerability from cvelistv5 – Published: 2026-08-15 05:56 – Updated: 2026-10-21 12:44
VLAI
EPSS
VEX
Title
iomap: guard io_size EOF trim against concurrent truncate underflow
Summary
In the Linux kernel, the following vulnerability has been resolved:
iomap: guard io_size EOF trim against concurrent truncate underflow
iomap: fix zero padding data issue in concurrent append writes
changed ioend accounting so that io_size tracks only valid data
within EOF. This trims io_size when a writeback range extends
past end_pos:
ioend->io_size += map_len;
if (ioend->io_offset + ioend->io_size > end_pos)
ioend->io_size = end_pos - ioend->io_offset;
However, if end_pos ends up below ioend->io_offset, the subtraction
becomes negative and is stored in size_t io_size, causing an unsigned
wrap to a huge value. This can happen when writeback continues past
byte-level EOF up to a block-aligned range, or when a concurrent
truncate shrinks the file after end_pos was sampled in
iomap_writeback_handle_eof().
A wrapped io_size can mislead append detection and corrupt
completion-time size handling, since filesystem end_io paths consume
io_size for decisions such as on-disk EOF updates and unwritten/COW
completion ranges.
Fix this by clamping io_size to zero when EOF has moved to or before
the ioend start offset. This preserves the original intent of trimming
io_size to valid in-EOF data while avoiding the underflow.
Severity
8.8 (High)
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | |
|---|---|---|---|
| Linux | Linux |
Affected:
82c59a86a247a8970d353d10f52a37e5564fb137 , < cc1d6af0bee27d6595908b497424f338161299fc
(git)
Affected: 51d20d1dacbec589d459e11fc88fbca419f84a99 , < 1f38f65bf965fce9aa159d45c5347538f56c5973 (git) Affected: 51d20d1dacbec589d459e11fc88fbca419f84a99 , < 7f7780abb4c0fdc9a2603aea8e985ff14ee900e0 (git) Affected: 51d20d1dacbec589d459e11fc88fbca419f84a99 , < 55ec50d046c03b3724741957f7b007856e36dbe7 (git) Affected: 6.12.10 , < 6.12.114 (semver) |
|
| Linux | Linux |
Affected:
6.13
Unaffected: 0 , < 6.13 (semver) Unaffected: 6.12.114 , ≤ 6.12.* (semver) Unaffected: 6.18.40 , ≤ 6.18.* (semver) Unaffected: 7.1.5 , ≤ 7.1.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix) |
{
"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": "cc1d6af0bee27d6595908b497424f338161299fc",
"status": "affected",
"version": "82c59a86a247a8970d353d10f52a37e5564fb137",
"versionType": "git"
},
{
"lessThan": "1f38f65bf965fce9aa159d45c5347538f56c5973",
"status": "affected",
"version": "51d20d1dacbec589d459e11fc88fbca419f84a99",
"versionType": "git"
},
{
"lessThan": "7f7780abb4c0fdc9a2603aea8e985ff14ee900e0",
"status": "affected",
"version": "51d20d1dacbec589d459e11fc88fbca419f84a99",
"versionType": "git"
},
{
"lessThan": "55ec50d046c03b3724741957f7b007856e36dbe7",
"status": "affected",
"version": "51d20d1dacbec589d459e11fc88fbca419f84a99",
"versionType": "git"
},
{
"lessThan": "6.12.114",
"status": "affected",
"version": "6.12.10",
"versionType": "semver"
}
]
},
{
"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.13"
},
{
"lessThan": "6.13",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.114",
"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.114",
"versionStartIncluding": "6.12.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.40",
"versionStartIncluding": "6.13",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1.5",
"versionStartIncluding": "6.13",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "6.13",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\niomap: guard io_size EOF trim against concurrent truncate underflow\n\niomap: fix zero padding data issue in concurrent append writes\nchanged ioend accounting so that io_size tracks only valid data\nwithin EOF. This trims io_size when a writeback range extends\npast end_pos:\n\n ioend-\u003eio_size += map_len;\n if (ioend-\u003eio_offset + ioend-\u003eio_size \u003e end_pos)\n ioend-\u003eio_size = end_pos - ioend-\u003eio_offset;\n\nHowever, if end_pos ends up below ioend-\u003eio_offset, the subtraction\nbecomes negative and is stored in size_t io_size, causing an unsigned\nwrap to a huge value. This can happen when writeback continues past\nbyte-level EOF up to a block-aligned range, or when a concurrent\ntruncate shrinks the file after end_pos was sampled in\niomap_writeback_handle_eof().\n\nA wrapped io_size can mislead append detection and corrupt\ncompletion-time size handling, since filesystem end_io paths consume\nio_size for decisions such as on-disk EOF updates and unwritten/COW\ncompletion ranges.\n\nFix this by clamping io_size to zero when EOF has moved to or before\nthe ioend start offset. This preserves the original intent of trimming\nio_size to valid in-EOF data while avoiding the underflow."
}
],
"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 - On XFS/GFS2/NTFS backends exposed via nfsd or ksmbd, a remote client can trigger iomap buffered writeback by issuing concurrent WRITE and truncate/SETATTR operations over the network without local shell access.\nAC:L - The attacker controls both sides of the race by concurrently writing dirty pages and truncating the same file (local threads or parallel NFS/SMB requests); no uncontrollable memory layout or rare kernel configuration is required.\nPR:L - Exploitation requires write and truncate permission on the target file (authenticated NFS/SMB client or local unprivileged user with file write access); this is not a pre-authentication network code path.\nUI:N - No victim interaction is needed beyond the attacker\u0027s own write and truncate I/O; writeback is driven automatically by the VFS/page-cache path once pages are dirtied.\nS:U - Impact is confined to kernel/filesystem integrity within the same security authority (metadata corruption, incorrect extent completion, possible local privilege escalation), not a VM escape or cross-authority boundary.\nC:H - A wrapped io_size propagates into XFS completion paths (COW convert/end, unwritten conversion, append detection), potentially remapping or exposing unintended on-disk extents and data beyond the legitimate EOF-trimmed range.\nI:H - Huge bogus io_size drives xfs_reflink_convert_cow, xfs_reflink_end_cow, xfs_iomap_write_unwritten, and xfs_setfilesize with corrupted ranges, enabling incorrect on-disk metadata updates and file content modification.\nA:H - Corrupted ioend accounting can trigger pathological XFS extent walks, ASSERT failures, filesystem shutdown, or hung writeback during I/O completion, causing kernel oops or sustained denial of service."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-21T12:44:42.934Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/cc1d6af0bee27d6595908b497424f338161299fc"
},
{
"url": "https://git.kernel.org/stable/c/1f38f65bf965fce9aa159d45c5347538f56c5973"
},
{
"url": "https://git.kernel.org/stable/c/7f7780abb4c0fdc9a2603aea8e985ff14ee900e0"
},
{
"url": "https://git.kernel.org/stable/c/55ec50d046c03b3724741957f7b007856e36dbe7"
}
],
"title": "iomap: guard io_size EOF trim against concurrent truncate underflow",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-72367",
"datePublished": "2026-08-15T05:56:04.669Z",
"dateReserved": "2026-08-09T03:40:39.922Z",
"dateUpdated": "2026-10-21T12:44:42.934Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-72367",
"date": "2026-11-17",
"epss": "0.00601",
"percentile": "0.49402"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"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": "cc1d6af0bee27d6595908b497424f338161299fc",
"status": "affected",
"version": "82c59a86a247a8970d353d10f52a37e5564fb137",
"versionType": "git"
},
{
"lessThan": "1f38f65bf965fce9aa159d45c5347538f56c5973",
"status": "affected",
"version": "51d20d1dacbec589d459e11fc88fbca419f84a99",
"versionType": "git"
},
{
"lessThan": "7f7780abb4c0fdc9a2603aea8e985ff14ee900e0",
"status": "affected",
"version": "51d20d1dacbec589d459e11fc88fbca419f84a99",
"versionType": "git"
},
{
"lessThan": "55ec50d046c03b3724741957f7b007856e36dbe7",
"status": "affected",
"version": "51d20d1dacbec589d459e11fc88fbca419f84a99",
"versionType": "git"
},
{
"lessThan": "6.12.114",
"status": "affected",
"version": "6.12.10",
"versionType": "semver"
}
]
},
{
"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.13"
},
{
"lessThan": "6.13",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.114",
"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"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\niomap: guard io_size EOF trim against concurrent truncate underflow\n\niomap: fix zero padding data issue in concurrent append writes\nchanged ioend accounting so that io_size tracks only valid data\nwithin EOF. This trims io_size when a writeback range extends\npast end_pos:\n\n ioend-\u003eio_size += map_len;\n if (ioend-\u003eio_offset + ioend-\u003eio_size \u003e end_pos)\n ioend-\u003eio_size = end_pos - ioend-\u003eio_offset;\n\nHowever, if end_pos ends up below ioend-\u003eio_offset, the subtraction\nbecomes negative and is stored in size_t io_size, causing an unsigned\nwrap to a huge value. This can happen when writeback continues past\nbyte-level EOF up to a block-aligned range, or when a concurrent\ntruncate shrinks the file after end_pos was sampled in\niomap_writeback_handle_eof().\n\nA wrapped io_size can mislead append detection and corrupt\ncompletion-time size handling, since filesystem end_io paths consume\nio_size for decisions such as on-disk EOF updates and unwritten/COW\ncompletion ranges.\n\nFix this by clamping io_size to zero when EOF has moved to or before\nthe ioend start offset. This preserves the original intent of trimming\nio_size to valid in-EOF data while avoiding the underflow."
}
],
"id": "CVE-2026-72367",
"lastModified": "2026-10-21T13:19:36.047",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2026-08-15T06:22:10.117",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/1f38f65bf965fce9aa159d45c5347538f56c5973"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/55ec50d046c03b3724741957f7b007856e36dbe7"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7f7780abb4c0fdc9a2603aea8e985ff14ee900e0"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/cc1d6af0bee27d6595908b497424f338161299fc"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-07T04:37:23+00:00",
"cve": "CVE-2026-72367",
"id": "CVE-2026-72367",
"initial_release_date": "2026-08-15T00:00:00+00:00",
"product_status:known_affected": "1",
"product_status:known_not_affected": "199",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: iomap: guard io_size EOF trim against concurrent truncate underflow",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-72367.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-10-21T17:12:24Z",
"cve": "CVE-2026-72367",
"id": "CVE-2026-72367",
"initial_release_date": "2026-09-01T17:14:05Z",
"product_status:known_affected": "42",
"product_status:known_not_affected": "321",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-72367",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-72367.json",
"version": "5"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…