CVE-2026-99694: ocfs2: do not index before the entry array when dividing an empty bucket

Published Nov 20, 2026
·
Updated

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

ocfs2: do not index before the entry array when dividing an empty bucket

ocfs2dividexattrbucket() appends an empty bucket carrying a sentinel hash when the source bucket has no divide position, taking that hash from xhentries[start - 1]. ocfs2xattrfinddividepos() 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 xhentries[-1].

That is outside the countedbyle(xhcount) bounds of xhentries[] and lands on the header, so the value picked up is xhcount | xhfreestart << 16. One above it is written into the new bucket's xhentries[0] and committed, which leaves a bucket whose first hash does not follow the bucket before it. ocfs2xattrbucketfind() binary searches on xhentries[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 ecpos, which then claims a hash range it does not cover.

Read xhentries[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 ocfs2checkxattrbucketcollision(), which reports no collision for one, through ocfs2addnewxattrbucket() and ocfs2extendxattrbucket(). 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.

Affected Software

3 affected componentsFixes available
linux/kernel>=2.6.28<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Compensating control

    In ocfs2_divide_xattr_bucket(), read xh_entries[0] instead of indexing before the entry array when dividing an empty bucket.

Frequently Asked Questions

1

What filesystem state is required to trigger the issue?

The problem occurs when ocfs2_divide_xattr_bucket() divides an empty extended-attribute bucket. In that case, the divide-position lookup can return zero, causing the code to read the entry immediately before the empty entry array.

2

What symptoms can result from the corrupted bucket metadata?

A stored extended attribute may incorrectly appear absent to getxattr(), returning -ENODATA. Subsequent inserts can be directed to the wrong bucket and may create duplicate copies of an attribute name.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203