{"id":"CVE-2026-99694","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:\n\nocfs2: do not index before the entry array when dividing an empty bucket\n\nocfs2_divide_xattr_bucket() appends an empty bucket carrying a sentinel\nhash when the source bucket has no divide position, taking that hash\nfrom xh_entries[start - 1].  ocfs2_xattr_find_divide_pos() returns count\nwhen every entry shares one hash, and its loop does not run at all for\ncount \u003c 2, so an empty bucket comes back with start == count == 0 and\nthe read is xh_entries[-1].\n\nThat is outside the __counted_by_le(xh_count) bounds of xh_entries[] and\nlands on the header, so the value picked up is\nxh_count | xh_free_start \u003c\u003c 16.  One above it is written into the new\nbucket's xh_entries[0] and committed, which leaves a bucket whose first\nhash does not follow the bucket before it.  ocfs2_xattr_bucket_find()\nbinary searches on xh_entries[0], so the broken key hides the range the\nsentinel was meant to cover: getxattr() answers -ENODATA for an\nattribute that is stored, and an insert can go to the wrong bucket and\nleave two copies of a name.  The cross cluster divide hands the same\nvalue back as a tree record's e_cpos, which then claims a hash range it\ndoes not cover.\n\nRead xh_entries[0] instead.  The branch is only reached when every entry\nshares one hash, so for a non-empty bucket it holds the same value, and\nfor an empty one it is the slot that carries the bucket key.\n\nAn empty bucket reaches the divide from\nocfs2_check_xattr_bucket_collision(), which reports no collision for\none, through ocfs2_add_new_xattr_bucket() and\nocfs2_extend_xattr_bucket().  It does not take a failed set to get\nthere: a divide that finds no position is itself what leaves an empty\nsentinel bucket behind, and a later extend can pick it as the target.","modified":"2026-11-20T07:01:10.131576599Z","published":"2026-11-20T05:50:38.090Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99694.json"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/58308e76c036822c78947efbbdcb800c1df6f6b2"},{"type":"WEB","url":"https://git.kernel.org/stable/c/7133a0d0954c109f1764ebf8ab32d7e757a6c587"},{"type":"WEB","url":"https://git.kernel.org/stable/c/7148fa383fb000d3125989ff3e63f3458a33591d"},{"type":"WEB","url":"https://git.kernel.org/stable/c/b710975d07b049c957ba6b93985b1cf9b169ad6e"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99694.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99694"}],"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"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"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"}}],"schema_version":"1.9.2"}