CVE-2026-72367
- Source
- https://cve.org/CVERecord?id=CVE-2026-72367
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-72367.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-72367
- Downstream
- Published
- 2026-08-15T05:56:04Z
- Modified
- 2026-10-28T02:31:12Z
- Severity
-
- 8.8 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- iomap: guard io_size EOF trim against concurrent truncate underflow
- Details
-
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.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/72xxx/CVE-2026-72367.json" }- References
-
- https://git.kernel.org/stable/c/1f38f65bf965fce9aa159d45c5347538f56c5973
- https://git.kernel.org/stable/c/55ec50d046c03b3724741957f7b007856e36dbe7
- https://git.kernel.org/stable/c/7f7780abb4c0fdc9a2603aea8e985ff14ee900e0
- https://git.kernel.org/stable/c/cc1d6af0bee27d6595908b497424f338161299fc
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/72xxx/CVE-2026-72367.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-72367
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced82c59a86a247a8970d353d10f52a37e5564fb137Fixedcc1d6af0bee27d6595908b497424f338161299fc
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced51d20d1dacbec589d459e11fc88fbca419f84a99Fixed1f38f65bf965fce9aa159d45c5347538f56c5973Fixed7f7780abb4c0fdc9a2603aea8e985ff14ee900e0Fixed55ec50d046c03b3724741957f7b007856e36dbe7
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced6.12.10Fixed6.12.114