PT-2026-152574

CVE-2026-99694

·

Published

2026-11-20

·

Updated

2026-11-20

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

In the Linux kernel, the following vulnerability has been resolved:
ocfs2: do not index before the entry array when dividing an empty bucket
ocfs2 divide xattr bucket() appends an empty bucket carrying a sentinel hash when the source bucket has no divide position, taking that hash from xh entries[start - 1]. ocfs2 xattr find divide pos() returns count when every entry shares one hash, and its loop does not run at all for count < 2, so an empty bucket comes back with start == count == 0 and the read is xh entries[-1].
That is outside the counted by le(xh count) bounds of xh entries[] and lands on the header, so the value picked up is xh count | xh free start << 16. One above it is written into the new bucket's xh entries[0] and committed, which leaves a bucket whose first hash does not follow the bucket before it. ocfs2 xattr bucket find() binary searches on xh entries[0], so the broken key hides the range the sentinel was meant to cover: getxattr() answers -ENODATA for an attribute that is stored, and an insert can go to the wrong bucket and leave two copies of a name. The cross cluster divide hands the same value back as a tree record's e cpos, which then claims a hash range it does not cover.
Read xh entries[0] instead. The branch is only reached when every entry shares one hash, so for a non-empty bucket it holds the same value, and for an empty one it is the slot that carries the bucket key.
An empty bucket reaches the divide from ocfs2 check xattr bucket collision(), which reports no collision for one, through ocfs2 add new xattr bucket() and ocfs2 extend xattr bucket(). It does not take a failed set to get there: a divide that finds no position is itself what leaves an empty sentinel bucket behind, and a later extend can pick it as the target.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾