ocfs2: fix UBSAN array-index-out-of-bounds in ocfs2_sum_rightmost_rec
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ dcd0538ff4e854fa9d7f4630b359ca8fdb5cb5a8 · < 452a8467be8143747292218212671deeb186d2ae| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's ocfs2 code can index outside an inode's embedded extent list when on-disk metadata is corrupt. Someone able to corrupt that metadata can trigger a UBSAN panic on the next write to the affected file. The input does not specify whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with ocfs2 should check their systems; affected versions are not specified.