PT-2026-152521

CVE-2026-99641

·

تاريخ النشر

2026-11-20

·

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

2026-11-20

الوصف من

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

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

In the Linux kernel, the following vulnerability has been resolved:
ovl: fail the mount if the casefold flag has changed
An unprivileged user in a user namespace can repeatedly trigger a kernel warning with their own overlay mounts. They do so by changing the casefold flag of the topmost layer's empty root, the top directory of that layer, after the layers are set and before the mount is created.
The casefold flag of a directory makes name lookups in that directory case-insensitive. All layers of an overlay must agree on casefolding.
ovl mount dir check() reads the casefold flag of a layer root when fsconfig() sets that layer, and saves the result in ofs->casefold. The mount is created later, by another fsconfig() call with FSCONFIG CMD CREATE.
The casefold flag of an empty directory can be changed.
The casefold flag of the overlay root must match ofs->casefold. ovl get root() copies the flag from the topmost layer root, as it is when the mount is created. On a mismatch, ovl get root() only does a WARN ON(), and the mount continues. The check is not a WARN ON ONCE(), so each such mount warns again.
An unprivileged user needs CONFIG UNICODE, and a tmpfs mounted with the casefold option in their namespace.
Reproduced by changing the casefold flag of the empty upper directory after the layers were set and before FSCONFIG CMD CREATE, with tmpfs and ext4 layers, and as uid 1000 in a user namespace.
Fix this by replacing the WARN ON() with a check that fails the mount with -EINVAL.
المورّدون
المنتجات المتأثرة
المعرّفات ذات الصلة
وجدت خطأً في الوصف؟ لديك ما تضيفه؟ لا تتردد في مراسلتنا 👾