PT-2026-152576

CVE-2026-99696

·

تاريخ النشر

2026-11-20

·

تاريخ التحديث

2026-11-20

الوصف من

الدرجة
N/A
غير متوفر

لا تتوفر حاليًا تقييمات أو مقاييس للخطورة. سنحدّث المعلومات المقابلة في الصفحة فور توفرها.

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.
المورّدون
المنتجات المتأثرة
المعرّفات ذات الصلة
وجدت خطأً في الوصف؟ لديك ما تضيفه؟ لا تتردد في مراسلتنا 👾