CVE-2026-72159

UnknownEPSS 0.21%

Last modified

CVE-2026-72159 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.

Description

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().

Metrics

EPSS Probability
0.21%

11.6th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= b657c95c11088d77fc1bfc9c84d940f778bf9d12, < 416d3e5f8a30ed04fe21ba7dc73c2841c3b56265; >= b657c95c11088d77fc1bfc9c84d940f778bf9d12, < ed0f938f946f16b772e99cb8c277ab57828e5be4; >= b657c95c11088d77fc1bfc9c84d940f778bf9d12, < 83f6756a7b71adec0a41ae68e079a38906d59c6c; >= b657c95c11088d77fc1bfc9c84d940f778bf9d12, < 38c1ef7ce50eb4af0f89038b8aba12396ddb9233; >= b657c95c11088d77fc1bfc9c84d940f778bf9d12, < d837068eefbc2651fe5789bf75a0f945710f7b8e; >= b657c95c11088d77fc1bfc9c84d940f778bf9d12, < 2174c68f623b74bd8690a4a6a4a52882d8ac3dc3; >= b657c95c11088d77fc1bfc9c84d940f778bf9d12, < 3bfeb436d4be6a2beb56cab344770e93e6b07260; >= b657c95c11088d77fc1bfc9c84d940f778bf9d12, < 7ebc672fab7a76e1e47e0f2fc1ee48118d27fde4
LinuxLinux2.6.29

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-72159?
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().
How severe is CVE-2026-72159?
Severity scoring for CVE-2026-72159 is pending analysis. The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2026-72159?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-72159?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST