Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-72159: ocfs2: reject non-inline dinodes with i_size and zero i_clusters

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Fixed version: Linux Linux 2174c68f623b74bd8690a4a6a4a52882d8ac3dc3, 38c1ef7ce50eb4af0f89038b8aba12396ddb9233, 3bfeb436d4be6a2beb56cab344770e93e6b07260.

Low priority for now. Upgrade to Linux Linux 2174c68f623b74bd8690a4a6a4a52882d8ac3dc3, 38c1ef7ce50eb4af0f89038b8aba12396ddb9233, 3bfeb436d4be6a2beb56cab344770e93e6b07260 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: ocfs2: reject non-inline dinodes with i_size and zero i_clusters On a volume mounted without OCFS2_FEATURE_INCOMPAT_SPARSE_ALLOC, a non-inline regular file with non-zero i_size and zero i_clusters is structurally malformed: the extent map declares no allocated clusters yet the size header claims content exists. Keep rejecting that shape, but express it through a shared predicate so the same invariant is available to normal inode reads and online filecheck. The same zero-cluster shape is also malformed for non-inline directories. ocfs2 directory growth allocates backing storage before advancing i_size, and ocfs2_dir_foreach_blk_el() later walks until ctx->pos reaches i_size_read(inode). A forged directory dinode with a huge i_size and no clusters would repeatedly fail on holes while advancing through the claimed size. Sparse regular files remain exempt: on sparse-alloc volumes, truncate can legitimately grow i_size without allocating clusters. System inodes and inline-data dinodes also retain their separate storage rules. Mirror the check in ocfs2_filecheck_validate_inode_block() as well. filecheck reports through its own error namespace, so malformed size/cluster state is logged as a filecheck invalid-inode result rather than via ocfs2_error(), but it must not proceed into ocfs2_populate_inode().

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-72159

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.29affected
    • b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before 416d3e5f8a30ed04fe21ba7dc73c2841c3b56265affected · git
    • b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before ed0f938f946f16b772e99cb8c277ab57828e5be4affected · git
    • b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before 83f6756a7b71adec0a41ae68e079a38906d59c6caffected · git
    • b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before 38c1ef7ce50eb4af0f89038b8aba12396ddb9233affected · git
    • b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before d837068eefbc2651fe5789bf75a0f945710f7b8eaffected · git
    • b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before 2174c68f623b74bd8690a4a6a4a52882d8ac3dc3affected · git
    • b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before 3bfeb436d4be6a2beb56cab344770e93e6b07260affected · git
    • b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before 7ebc672fab7a76e1e47e0f2fc1ee48118d27fde4affected · git
    • before 2.6.29not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72156Aug 15, 2026 · fpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header()
    0Monitor
  • ← EarlierCVE-2026-72158Aug 15, 2026 · fpga: dfl: add bounds check in dfh_get_param_size()
    0Monitor
  • Later →CVE-2026-72161Aug 15, 2026 · ocfs2: add journal NULL check in ocfs2_checkpoint_inode()
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2174c68f623b74bd8690a4a6a4a52882d8ac3dc3Vendor (CNA)
Linux Linux38c1ef7ce50eb4af0f89038b8aba12396ddb9233Vendor (CNA)
Linux Linux3bfeb436d4be6a2beb56cab344770e93e6b07260Vendor (CNA)
Linux Linux416d3e5f8a30ed04fe21ba7dc73c2841c3b56265Vendor (CNA)
Linux Linux7ebc672fab7a76e1e47e0f2fc1ee48118d27fde4Vendor (CNA)
Linux Linux83f6756a7b71adec0a41ae68e079a38906d59c6cVendor (CNA)
Linux Linuxd837068eefbc2651fe5789bf75a0f945710f7b8eVendor (CNA)
Linux Linuxed0f938f946f16b772e99cb8c277ab57828e5be4Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records