← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-72162

Last refreshed2026-10-23

Status: UPDATED  |  Advisory ID: CVE-2026-72162

Key Details

CVECVE-2026-72162
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-21
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

In the Linux kernel, the following vulnerability has been resolved:

ocfs2: fix UBSAN array-index-out-of-bounds in ocfs2_sum_rightmost_rec

[BUG]

On-disk corruption setting l_next_free_rec to 0 in an inode's embedded

extent list triggers a UBSAN panic on the next write to that file.

[CAUSE]

ocfs2_sum_rightmost_rec() computes

i = le16_to_cpu(el->l_next_free_rec) - 1

and accesses el->l_recs[i] without validating i. When l_next_free_rec

is 0, i becomes -1; when l_next_free_rec exceeds l_count, i falls

past the end of the array. Either case violates the

__counted_by_le(l_count) annotation on l_recs[] and triggers UBSAN.

[FIX]

Validate the inode's embedded extent list when the inode is read, in

ocfs2_validate_inode_block(): l_count must be non-zero and no larger

than the inode block can hold, and l_next_free_rec must not exceed

l_count. A corrupt list is rejected at read time, before the b-tree

code can index l_recs[] out of bounds. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-72162
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-72162
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.