Skip to content
Systems

CVE-2026-72367

HIGH
High
EPSS 0.58%Patch availableAug 17, 2026

Linux iomap underflow bug can corrupt files during concurrent write/truncate

common questions

Is CVE-2026-72367 being exploited?

Not confirmed. CVE-2026-72367 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.58% probability of exploitation in the next 30 days.

How severe is CVE-2026-72367?

CVE-2026-72367 is rated High. 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-72367?

Yes. A fix has been recorded for CVE-2026-72367. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72367 affect?

CVE-2026-72367 affects Linux kernel (iomap subsystem), Linux distributions using affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72367?

Apply vendor/kernel updates and reboot affected hosts promptly

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (iomap subsystem)Linux distributions using affected kernels
impact

Local concurrent writes/truncates can underflow io_size, causing unsigned wrap and file/data corruption or loss during writeback.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 51d20d1dacbec589d459e11fc88fbca419f84a99 and < 1f38f65bf965fce9aa159d45c5347538f56c5973
  • affected>= 51d20d1dacbec589d459e11fc88fbca419f84a99 and < 7f7780abb4c0fdc9a2603aea8e985ff14ee900e0
  • affected>= 51d20d1dacbec589d459e11fc88fbca419f84a99 and < 55ec50d046c03b3724741957f7b007856e36dbe7
  • affected82c59a86a247a8970d353d10f52a37e5564fb137
  • affected>= 6.12.10 and < 6.13
  • affected6.13
vendor says fixed in< 6.13, >= 6.18.40 and <= 6.18.*, >= 7.1.5 and <= 7.1.*, >= 7.2 and <= *

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free