cve.bz

CVE-2026-72160 linux linux

8.8 highEPSS 0.7%Fix available

High (8.8) in linux linux. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
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().

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.261
  • Linux Linux: fixed in 5.15.212
  • Linux Linux: fixed in 6.1.178
  • Linux Linux: fixed in 6.6.145
  • Linux Linux: fixed in 6.12.97
  • Linux Linux: fixed in 6.18.40
  • Linux Linux: fixed in 7.1.5
  • Linux Linux: fixed in 7.2
  • Debian, Ubuntu, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-72160 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-72160?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-72160?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-72160 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux2.6.29 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.261
Linux5.155.15.212
Linux6.16.1.178
Linux6.66.6.145
Linux6.126.12.97
Linux6.186.18.40
Linux7.17.1.5
Linuxlater releases7.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.180-1DEBIAN-CVE-2026-72160
Debian13linux6.12.100-1DEBIAN-CVE-2026-72160
Debian14linux7.1.5-1DEBIAN-CVE-2026-72160
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-72160
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-72160
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-72160
Ubuntu22.04:LTSlinux5.15.0-198.208UBUNTU-CVE-2026-72160 USN-8875-1
Ubuntu22.04:LTSlinux-aws5.15.0-1117.124UBUNTU-CVE-2026-72160 USN-8875-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-72160 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1123.132UBUNTU-CVE-2026-72160 USN-8875-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-72160 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1122.131UBUNTU-CVE-2026-72160 USN-8876-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-72160 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1118.128UBUNTU-CVE-2026-72160 USN-8877-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-72160 USN-9024-1
80 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquita23linux-lts6.1.182-r0BELL-CVE-2026-72160
Alpaquita25linux-lts6.12.103-r0BELL-CVE-2026-72160
Alpaquitastreamlinux-lts6.18.43-r0BELL-CVE-2026-72160

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate severity flaw was found in the Linux kernel's OCFS2 file system. The ocfs2_validate_inode_block() function accepted on-disk dinodes whose i_mode type bits did not name one of the seven canonical POSIX file types, and ocfs2_populate_inode() copied such a mode verbatim into the in-core inode, where an unrecognized type fell through to the special-file inode operations. A local attacker able to supply a crafted OCFS2 file system image, which requires local access and privileges sufficient to present such metadata, could use a malformed inode to bypass existing validation, causing unexpected system behavior or instability and a denial of service. Red Hat rated this flaw CVSS 3.1 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) because exploitation requires local access and the impact is limited to system availability; this is lower than the upstream CVE record severity of 8.8, which assumes a network attack vector that the technical evidence does not support. All currently assessed Red Hat product streams (Red Hat Enterprise Linux 6 through 10, including kernel-rt, and Red Hat In-Vehicle OS) are recorded as not affected because the vulnerable code is not present in those shipped kernels.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-72160.

References

Check your stackJSON