CVE-2026-99696: Linux kernel · ocfs2: find the xattr entry again after defragmenting a bucket
Source GCVE Database
Not known to be exploited · fixed in b839d9913b56f0d769dced34cdfbe02a009b3bf1 : patch Linux kernel soon.
Data as of 20 Nov 2026, 07:34 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in b839d9913b56f0d769dced34cdfbe02a009b3bf1, 89ef9cb4da160b5572e0e5b9cf930335117d561b, 9a40c050f58344615a0604701b5d299519833163 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Linux kernel to b839d9913b56f0d769dced34cdfbe02a009b3bf1, 89ef9cb4da160b5572e0e5b9cf930335117d561b, 9a40c050f58344615a0604701b5d299519833163 or 8c107f10fe63fdec081c2ae471fc90b4d3376db6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: ocfs2: find the xattr entry again after defragmenting a bucket ocfs2_xattr_set_entry_bucket() hands loc.xl_entry to ocfs2_xa_set() twice: once for the bucket as it stands, and, if that reports -ENOSPC, once more after ocfs2_defrag_xattr_bucket() has packed the name/value pairs down. Defragmenting ends by sorting the entry array on xe_name_hash. Buckets are kept sorted, so the sort only permutes entries that share a hash, but lib/sort.c is an unstable heapsort and it does permute them. loc.xl_entry is an address inside xh_entries[], so afterwards it denotes whichever entry landed in that slot rather than the one the search found. The second ocfs2_xa_set() then works on the wrong entry. Nothing on that path compares the entry's name with xi->xi_name, so what happens depends on how the two entries compare in size: ocfs2_xa_reuse_entry() trips its BUG_ON() when the padded name sizes differ, and otherwise the new value is written into the neighbouring attribute's value slot while the attribute being set is left untouched. setxattr() reports success either way. Remember the entry's hash before defragmenting and look the entry up again afterwards, the way ocfs2_xattr_bucket_find() does. An entry that cannot be found again means the bucket no longer holds what the search found, so fail with -EFSCORRUPTED rather than writing through the stale pointer.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99696 (opens in a new tab)
- git.kernel.org/stable/c/89ef9cb4da160b5572e0e5b9cf930335117d561b (opens in a new tab)
- git.kernel.org/stable/c/8c107f10fe63fdec081c2ae471fc90b4d3376db6 (opens in a new tab)
- git.kernel.org/stable/c/9a40c050f58344615a0604701b5d299519833163 (opens in a new tab)
- git.kernel.org/stable/c/b839d9913b56f0d769dced34cdfbe02a009b3bf1 (opens in a new tab)