PT-2026-151633
CVE-2026-99422
·
Published
2026-11-19
·
Updated
2026-11-19
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
ovl: use the pinned upper dir in ovl fix origin()
Renames made directly on the upper filesystem during a lookup crash the
kernel.
A dentry that is passed to vfs setxattr() must be pinned.
ovl fix origin() passes upper->d parent to ovl set impure() without a
reference, and the lookup holds no lock of the upper directory. A
rename on the upper filesystem changes d parent, and only the child
pins the new parent, so a second rename and an rmdir free it.
With delays in ovl fix origin() and ovl set impure(), renaming the upper
directory twice and removing the intermediate parent during the lookup
of a merge directory without an origin xattr gave a KASAN
use-after-free in vfs setxattr().
Fix this by passing the upper dentry that the overlay parent holds.
[amir: add helper ovl set impure dir()]
Found an issue in the description? Have something to add? Feel free to write us 👾