CVE-2026-72160: ocfs2: reject dinodes with non-canonical i_mode type
Noroxi assessment
Priority: Monitor (action score 35/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.65% (FIRST EPSS); higher than 51.7% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 157d31ef45038d89cd19620105e082d43c8e41e0, 2e3aac33988ef4e4170141db8e995693ea38357c, 4db3b6a2a8ecf2a89d26a4090ace4072c6fad050.
Low priority for now. Upgrade to Linux Linux 157d31ef45038d89cd19620105e082d43c8e41e0, 2e3aac33988ef4e4170141db8e995693ea38357c, 4db3b6a2a8ecf2a89d26a4090ace4072c6fad050 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 dinodes with non-canonical i_mode type Patch series "ocfs2: harden inode validators against forged metadata", v2. This series adds three structural checks to OCFS2 dinode validation so malformed on-disk fields are rejected before ocfs2_populate_inode() copies them into the in-core inode. The checks cover: - i_mode values whose type bits do not name a canonical POSIX file type; - non-device dinodes whose id1.dev1.i_rdev field is non-zero; and - non-inline dinodes that claim non-zero i_size while i_clusters is zero, covering directories unconditionally and regular files on non-sparse volumes. The normal read path reports these through ocfs2_error(), matching the existing suballoc-slot, inline-data, chain-list, and refcount checks. The online filecheck path uses the same structural predicates but keeps its own reporting contract, returning OCFS2_FILECHECK_ERR_INVALIDINO instead of calling ocfs2_error(). This patch (of 3): ocfs2_validate_inode_block() currently accepts any non-zero i_mode value. ocfs2_populate_inode() then copies that mode verbatim into inode->i_mode and dispatches on i_mode & S_IFMT to the file/dir/symlink/special_file iops; an unrecognised type falls through to ocfs2_special_file_iops and init_special_inode(). Reject dinodes whose type bits do not name one of the seven canonical POSIX file types. Use fs_umode_to_ftype(), the same generic file-type conversion helper OCFS2 already uses for directory entries, so the accepted inode type set matches the kernel file-type vocabulary instead of open-coding a local switch. Apply the same structural check to the online filecheck read path. filecheck keeps its own error namespace, so it reports malformed i_mode through the filecheck logger and OCFS2_FILECHECK_ERR_INVALIDINO instead of calling ocfs2_error(), but it must not allow a malformed dinode to proceed into ocfs2_populate_inode().
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- —
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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 helpAffected 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 2e3aac33988ef4e4170141db8e995693ea38357caffected · git
- b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before fb024ea29f6cb1f01745e5f2e31646f3acb9aa6faffected · git
- b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before 157d31ef45038d89cd19620105e082d43c8e41e0affected · git
- b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before a5b555bcabbb0aff8745ad181768eaf9d964c1eeaffected · git
- b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before 82afe13558354390d8a592a5334d5f4fd72c0e5caffected · git
- b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before 4db3b6a2a8ecf2a89d26a4090ace4072c6fad050affected · git
- b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before b858f2d57cfc9d57ce61b86051d603dc0ebccd40affected · git
- b657c95c11088d77fc1bfc9c84d940f778bf9d12 and later · before 5366a017099c6a3c443be908a05f26fd72af12a1affected · git
- before 2.6.29not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72157Aug 15, 2026 · net: thunderbolt: Fix frags[] overflow by bounding frame_count35Monitor
- ← EarlierCVE-2026-72159Aug 15, 2026 · ocfs2: reject non-inline dinodes with i_size and zero i_clusters0Monitor
- Later →CVE-2026-72162Aug 15, 2026 · ocfs2: fix UBSAN array-index-out-of-bounds in ocfs2_sum_rightmost_rec31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 157d31ef45038d89cd19620105e082d43c8e41e0 | Vendor (CNA) |
| Linux Linux | 2e3aac33988ef4e4170141db8e995693ea38357c | Vendor (CNA) |
| Linux Linux | 4db3b6a2a8ecf2a89d26a4090ace4072c6fad050 | Vendor (CNA) |
| Linux Linux | 5366a017099c6a3c443be908a05f26fd72af12a1 | Vendor (CNA) |
| Linux Linux | 82afe13558354390d8a592a5334d5f4fd72c0e5c | Vendor (CNA) |
| Linux Linux | a5b555bcabbb0aff8745ad181768eaf9d964c1ee | Vendor (CNA) |
| Linux Linux | b858f2d57cfc9d57ce61b86051d603dc0ebccd40 | Vendor (CNA) |
| Linux Linux | fb024ea29f6cb1f01745e5f2e31646f3acb9aa6f | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2e3aac33988ef4e4170141db8e995693ea38357c
- git.kernel.org/stable/c/4db3b6a2a8ecf2a89d26a4090ace4072c6fad050
- git.kernel.org/stable/c/5366a017099c6a3c443be908a05f26fd72af12a1
- git.kernel.org/stable/c/82afe13558354390d8a592a5334d5f4fd72c0e5c
- git.kernel.org/stable/c/a5b555bcabbb0aff8745ad181768eaf9d964c1ee
- git.kernel.org/stable/c/b858f2d57cfc9d57ce61b86051d603dc0ebccd40
- git.kernel.org/stable/c/fb024ea29f6cb1f01745e5f2e31646f3acb9aa6f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.