CVE-2026-53341
Description
A flaw was found in the Linux kernel. This vulnerability, a Use-After-Free (UAF), occurs in the fhandle component when the may_decode_fh() function accesses mount namespace information without proper locking. This creates a race condition that could be exploited by an attacker. The most severe consequence is a kernel crash, leading to a Denial of Service (DoS), but it could also result in an endless loop or the disclosure of sensitive information.
Statement
A use after free can occur in the fhandle permission path because may_decode_fh reads mount::mnt_ns without RCU protection while another thread can unmount and free the related mnt_namespace after an RCU grace period. A local attacker that can reach open_by_handle_at() and race it with mount teardown may cause ns_capable() to dereference freed namespace memory through mnt_namespace::user_ns. For the CVSS the PR:L is used for the paranoid score because triggering requires local code execution and mount or file handle operations, but it does not necessarily require full host administrator privileges in all user namespace or reduced capability environments. The issue is not network reachable and requires a timing window, so AC:H is appropriate. Impact is at least local denial of service via kernel crash or hang, and in the worst case may allow confidentiality or integrity impact due to UAF in a permission check path.
Mitigation
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.7 | N/A | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | High | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory
The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.
Confidentiality
Technical Impact: Read Memory
Read operations on freed memory can sometimes leak sensitive information instead of causing a crash
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.