CVE-2026-72159 — ocfs2: reject non-inline dinodes with i_size and zero i_clusters
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().
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < 416d3e5f8a30ed04fe21ba7dc73c2841c3b56265≥ b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < ed0f938f946f16b772e99cb8c277ab57828e5be4≥ b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < 83f6756a7b71adec0a41ae68e079a38906d59c6c≥ b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < 38c1ef7ce50eb4af0f89038b8aba12396ddb9233≥ b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < d837068eefbc2651fe5789bf75a0f945710f7b8e≥ b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < 2174c68f623b74bd8690a4a6a4a52882d8ac3dc3≥ b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < 3bfeb436d4be6a2beb56cab344770e93e6b07260≥ b657c95c11088d77fc1bfc9c84d940f778bf9d12 and < 7ebc672fab7a76e1e47e0f2fc1ee48118d27fde4 and 1 moreversion 2.6.29 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/416d3e5f8a30ed04fe21ba7dc73c2841c3b56265
- git.kernel.org/stable/c/3bfeb436d4be6a2beb56cab344770e93e6b07260
- git.kernel.org/stable/c/7ebc672fab7a76e1e47e0f2fc1ee48118d27fde4
- git.kernel.org/stable/c/d837068eefbc2651fe5789bf75a0f945710f7b8e
- git.kernel.org/stable/c/ed0f938f946f16b772e99cb8c277ab57828e5be4
- git.kernel.org/stable/c/38c1ef7ce50eb4af0f89038b8aba12396ddb9233
- git.kernel.org/stable/c/83f6756a7b71adec0a41ae68e079a38906d59c6c
- git.kernel.org/stable/c/2174c68f623b74bd8690a4a6a4a52882d8ac3dc3
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-72159 is "ocfs2: reject non-inline dinodes with i_size and zero i_clusters", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.