ocfs2: fix UBSAN array-index-out-of-bounds in ocfs2_sum_rightmost_rec
CVE-2026-72162 · published 15 Aug 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-72162?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: dcd0538ff4e854fa9d7f4630b359ca8fdb5cb5a8 to < c286319746cef02bcce7384fda3a3f08989070d2, dcd0538ff4e854fa9d7f4630b359ca8fdb5cb5a8 to < 720fb324cf0f5116318cae7f75cb393d118ffb67, dcd0538ff4e854fa9d7f4630b359ca8fdb5cb5a8 to < 671889c553ea55e2da6a4f3b15f4c0fa40f2f0d1, dcd0538ff4e854fa9d7f4630b359ca8fdb5cb5a8 to < 858aa4965ffa8c0d4bb5dd835ac4f1c9a1dcab85
- Linux Linux: 2.6.22
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/c286319746cef02bcce7384fda3a3f08989070d2
- git.kernel.org/stable/c/720fb324cf0f5116318cae7f75cb393d118ffb67
- git.kernel.org/stable/c/671889c553ea55e2da6a4f3b15f4c0fa40f2f0d1
- git.kernel.org/stable/c/858aa4965ffa8c0d4bb5dd835ac4f1c9a1dcab85
- git.kernel.org/stable/c/452a8467be8143747292218212671deeb186d2ae
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON