Review reviewHigh

CVE-2026-53341

Linux Linux, linux kernel

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...

CVSS
7.8
EPSS
0.12%
2.14% percentile
CISA KEV
Not listed
Published
2026.07.01
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.12%
Technical severityCVSS 7.8

Vulnerability overview

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...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 620c266f394932e5decc4b34683a75dfc59dc2f4 < 15ea8dc42a02259d49dee38a658d40f60fcd75ed, >= 620c266f394932e5decc4b34683a75dfc59dc2f4 < 32138633e51e6db59e474765cf93268c92b42888, >= 620c266f394932e5decc4b34683a75dfc59dc2f4 < a8ed2c29fcfdac78db96c9da4e659c8a513f2a94, >= 620c266f394932e5decc4b34683a75dfc59dc2f4 < 40ab6644b99685755f740b872c00ef40d9aa870e, >= 6.11, >= 6.11 < 6.12.95, >= 6.13 < 6.18.36, >= 6.19 < 7.0.13, 7.1
Fixed versions
6.12.95, 6.18.36, 7.0.13

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416