In the Linux kernel, the following vulnerability has been resolved: ovl: use the pinned upper...
🔗 CVE IDs covered (1)
📋 Description
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()]
🔗 References (6)
- https://nvd.nist.gov/vuln/detail/CVE-2026-99422
- https://git.kernel.org/stable/c/17a540e65e567c8e4dd165a3ce5b592842ba5ab5
- https://git.kernel.org/stable/c/4f61ff2ebfb3d2967b83b6a4d456242244d5a61f
- https://git.kernel.org/stable/c/77c9b481faacf46b9d9282ffaa71afbac7acf819
- https://git.kernel.org/stable/c/b219cdaea16b2f3e8e13a63662d462addd8a2cd0
- https://github.com/advisories/GHSA-v4c4-7j95-qcj8