CVE-2026-99694

Source
https://cve.org/CVERecord?id=CVE-2026-99694
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99694.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99694
Published
2026-11-20T05:50:38Z
Modified
2026-11-20T07:01:10Z
Summary
ocfs2: do not index before the entry array when dividing an empty bucket
Details

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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99694.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
80bcaf3469b8aefd316d4ceb27d9af7cfbb0b913
Fixed
58308e76c036822c78947efbbdcb800c1df6f6b2
Fixed
7148fa383fb000d3125989ff3e63f3458a33591d
Fixed
b710975d07b049c957ba6b93985b1cf9b169ad6e
Fixed
7133a0d0954c109f1764ebf8ab32d7e757a6c587

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99694.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
2.6.28
Fixed
6.12.118
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.64
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.3.5

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99694.json"