Skip to content
Systems

CVE-2026-72160

8.8
High
EPSS 0.65%Patch availableAug 17, 2026

OCFS2 inode validation flaw allows forged dinodes to be accepted by the kernel.

common questions

Is CVE-2026-72160 being exploited?

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

How severe is CVE-2026-72160?

CVE-2026-72160 is rated High with a CVSS score of 8.8. 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-72160?

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

What does CVE-2026-72160 affect?

CVE-2026-72160 affects Linux kernel (OCFS2), Distributions with OCFS2 module, Cluster nodes using OCFS2, VM/removable media with OCFS2 images. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72160?

Install vendor kernel updates; avoid mounting untrusted OCFS2 images.

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

executive summary
technical analysis
affected
Linux kernel (OCFS2)Distributions with OCFS2 moduleCluster nodes using OCFS2VM/removable media with OCFS2 images
impact

Mounting or reading a crafted OCFS2 filesystem can cause kernel crashes, misinterpreted special files, or local privilege escalation via forged i_mode fields.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < 2e3aac33988ef4e4170141db8e995693ea38357c
  • affected>= b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < fb024ea29f6cb1f01745e5f2e31646f3acb9aa6f
  • affected>= b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < 157d31ef45038d89cd19620105e082d43c8e41e0
  • affected>= b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < a5b555bcabbb0aff8745ad181768eaf9d964c1ee
  • affected>= b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < 82afe13558354390d8a592a5334d5f4fd72c0e5c
  • affected>= b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < 4db3b6a2a8ecf2a89d26a4090ace4072c6fad050
  • affected>= b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < b858f2d57cfc9d57ce61b86051d603dc0ebccd40
  • affected>= b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < 5366a017099c6a3c443be908a05f26fd72af12a1
  • affected2.6.29
vendor says fixed in< 2.6.29, >= 5.10.261 and <= 5.10.*, >= 5.15.212 and <= 5.15.*, >= 6.1.178 and <= 6.1.*, >= 6.6.145 and <= 6.6.*, >= 6.12.97 and <= 6.12.*, >= 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