Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-53341— fhandle: fix UAF due to unlocked ->mnt_ns read in may_decode_fh()

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会开源的一款操作系统内核。 Linux kernel 6.11版本存在安全漏洞,该漏洞源于may_decode_fh()函数中未对mount::mnt_ns进行锁定读取,导致释放后重用漏洞,攻击者可能利用竞争条件造成信息泄露、无限循环或内核崩溃。

CVSS 7.8 · High EPSS 0.13% · P2

Affected Version Matrix 10

VendorProduct Version RangeStatus
Linux Linux 620c266f394932e5decc4b34683a75dfc59dc2f4< 15ea8dc42a02259d49dee38a658d40f60fcd75ed affected
620c266f394932e5decc4b34683a75dfc59dc2f4< 32138633e51e6db59e474765cf93268c92b42888 affected
620c266f394932e5decc4b34683a75dfc59dc2f4< a8ed2c29fcfdac78db96c9da4e659c8a513f2a94 affected
620c266f394932e5decc4b34683a75dfc59dc2f4< 40ab6644b99685755f740b872c00ef40d9aa870e affected
6.11 affected
< 6.11 unaffected
6.12.95≤ 6.12.* unaffected
6.18.36≤ 6.18.* unaffected
… +2 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-53341

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
fhandle: fix UAF due to unlocked ->mnt_ns read in may_decode_fh()
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会开源的一款操作系统内核。 Linux kernel 6.11版本存在安全漏洞,该漏洞源于may_decode_fh()函数中未对mount::mnt_ns进行锁定读取,导致释放后重用漏洞,攻击者可能利用竞争条件造成信息泄露、无限循环或内核崩溃。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux 620c266f394932e5decc4b34683a75dfc59dc2f4 ~ 15ea8dc42a02259d49dee38a658d40f60fcd75ed -
Linux Linux 6.11 -

II. Public POCs for CVE-2026-53341

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-53341

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-53341 (3)

Same Patch Batch · Linux · 2026-07-01 · 31 CVEs total

CVE-2026-53355 9.8 CRITICAL net: rds: clear i_sends on setup unwind
CVE-2026-53354 8.8 HIGH arm64: errata: Mitigate TLBI errata on various Arm CPUs
CVE-2026-53356 7.8 HIGH drm/i915/gem: Fix phys BO pread/pwrite with offset
CVE-2026-53329 7.0 HIGH drm/amd/display: Use krealloc_array() in dal_vector_reserve()
CVE-2026-53342 arm64: mm: call pagetable dtor when freeing hot-removed page tables
CVE-2026-53353 hsr: Remove WARN_ONCE() in hsr_addr_is_self().
CVE-2026-53352 signal: clear JOBCTL_PENDING_MASK for caller in zap_other_threads()
CVE-2026-53351 riscv/ptrace: Use USER_REGSET_NOTE_TYPE for REGSET_CFI
CVE-2026-53350 ASoC: wm_adsp: Fix NULL dereference when removing firmware controls
CVE-2026-53348 ASoC: SDCA: fix NULL pointer dereference in sdca_dev_unregister_functions
CVE-2026-53349 netfilter: nf_conntrack: destroy stale expectfn expectations on unregister
CVE-2026-53346 rust: arm64: set uwtable llvm module flag for CONFIG_UNWIND_TABLES
CVE-2026-53347 drm/virtio: Fix driver removal with disabled KMS
CVE-2026-53344 pinctrl: mcp23s08: Initialize mcp->dev and mcp->addr before regmap init
CVE-2026-53345 KVM: Don't WARN if memory is dirtied without a vCPU when the VM is dying
CVE-2026-53343 ARM: 9475/1: entry: use byte load for KASAN VMAP stack shadow
CVE-2026-53327 debugobjects: Do not fill_pool() if pi_blocked_on
CVE-2026-53340 i2c: imx: fix clock and pinctrl state inconsistency in runtime PM
CVE-2026-53339 i2c: qcom-cci: Fix NULL pointer dereference in cci_remove()
CVE-2026-53338 net: airoha: Add NULL check for of_reserved_mem_lookup() in airoha_qdma_init_hfwd_queues()

Showing top 20 of 31 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-53341

No comments yet


Leave a comment