CVE-2026-53341

published 1 Jul 2026 · updated 14 Nov 2026

fhandle: fix UAF due to unlocked ->mnt_ns read in may_decode_fh()

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel a8ed2c29fcfdac78db96c9da4e659c8a513f2a94, Kernel 15ea8dc42a02259d49dee38a658d40f60fcd75ed, Kernel 32138633e51e6db59e474765cf93268c92b42888 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: fhandle: fix UAF due to unlocked ->mnt_ns read in may_decode_fh() may_decode_fh() accesses mount::mnt_ns without holding any locks; that means the mount can concurrently be unmounted, and the mnt_namespace can concurrently be freed after an RCU grace period. This race can happens as follows, assuming that the mount point was created by open_tree(..., OPEN_TREE_CLONE): thread 1 thread 2 RCU __do_sys_open_by_handle_at do_handle_open handle_to_path may_decode_fh is_mounted [mount::mnt_ns access] [mount::mnt_ns access] __do_sys_close fput_close_sync __fput dissolve_on_fput umount_tree class_namespace_excl_destructor namespace_unlock free_mnt_ns mnt_ns_tree_remove call_rcu(mnt_ns_release_rcu) mnt_ns_release_rcu mnt_ns_release kfree [mnt_namespace::user_ns access] **UAF** Fix it by taking rcu_read_lock() around the mount::mnt_ns access, like in __prepend_path(). Additionally, document the semantics of mount::mnt_ns, and use WRITE_ONCE() for writers that can race with lockless readers. This bug is unreachable unless one of the following is set: - CONFIG_PREEMPTION - CONFIG_RCU_STRICT_GRACE_PERIOD because it requires an RCU grace period to happen during a syscall without an explicit preemption. This doesn't seem to have interesting security impact; worst-case, it could leak the result of an integer comparison to userspace (from the level check in cap_capable()), cause an endless loop, or crash the kernel by dereferencing an invalid address.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=620c266f394932e5decc4b34683a75dfc59dc2f4 <a8ed2c29fcfdac78db96c9da4e659c8a513f2a94, >=620c266f394932e5decc4b34683a75dfc59dc2f4 <15ea8dc42a02259d49dee38a658d40f60fcd75ed, >=620c266f394932e5decc4b34683a75dfc59dc2f4 <32138633e51e6db59e474765cf93268c92b42888, >=620c266f394932e5decc4b34683a75dfc59dc2f4 <40ab6644b99685755f740b872c00ef40d9aa870e, =6.11a8ed2c29fcfdac78db96c9da4e659c8a513f2a94, 15ea8dc42a02259d49dee38a658d40f60fcd75ed, 32138633e51e6db59e474765cf93268c92b42888, 40ab6644b99685755f740b872c00ef40d9aa870e
linux-kernel: Kernel>=6.13.0 <6.18.36, >=6.19.0 <7.0.13, >=6.11.0 <6.12.956.18.36, 7.0.13, 6.12.95

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-53341 severity on Zeptric[![CVE-2026-53341](https://zeptric.io/badge/cve/CVE-2026-53341.svg)](https://zeptric.io/cve/CVE-2026-53341)