Skip to content
Threat Brief

← All advisories

CVE-2026-99696

Severity unknownNo known exploitationFix available

ocfs2: find the xattr entry again after defragmenting a bucket

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 012255961c9ecfe22b7a1df47ac26ab37818cb1e before 89ef9cb4da160b5572e0e5b9cf930335117d561b89ef9cb4da160b5572e0e5b9cf930335117d561bCVE Program
LinuxLinuxfrom 012255961c9ecfe22b7a1df47ac26ab37818cb1e before 8c107f10fe63fdec081c2ae471fc90b4d3376db68c107f10fe63fdec081c2ae471fc90b4d3376db6CVE Program
LinuxLinuxfrom 012255961c9ecfe22b7a1df47ac26ab37818cb1e before 9a40c050f58344615a0604701b5d2995198331639a40c050f58344615a0604701b5d299519833163CVE Program
LinuxLinuxfrom 012255961c9ecfe22b7a1df47ac26ab37818cb1e before b839d9913b56f0d769dced34cdfbe02a009b3bf1b839d9913b56f0d769dced34cdfbe02a009b3bf1CVE Program
LinuxLinux2.6.28Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 2.6.28Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references