In the Linux kernel, the following vulnerability has been resolved:
fs/xattr: missing fdput() in fremovexattr error path
In the Linux kernel, the fremovexattr() syscall calls fdget() to acquire a
file reference but returns early without calling fdput() when
strncpy_from_user() fails on the name argument. In multi-threaded processes
where fdget() takes the slow path, this permanently leaks one
file reference per call, pinning the struct file and associated kernel
objects in memory. An unprivileged local user can exploit this to cause
kernel memory exhaustion. The issue was inadvertently fixed by commit
a71874379ec8 ("xattr: switch to CLASS(fd)").
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can let a local unprivileged user steadily leak kernel file references until memory is exhausted. The business impact is denial of service, not data theft, based on the supplied sources. Public severity and CVSS were not provided.
Executive priority
Treat this as a targeted availability risk. It is not currently cited as exploited, but shared Linux infrastructure should be patched on the next normal security cycle, faster for multi-tenant or untrusted workload environments.
Technical view
fremovexattr() obtains a file reference with fdget(), then may return early when copying the xattr name from user space fails. That error path missed fdput(), leaking one file reference per affected call on the slow path in multi-threaded processes.
Likely exposure
Exposure is primarily Linux systems allowing untrusted local users or workloads. Multi-user servers, shared development hosts, and container hosts deserve attention. Exact distribution impact depends on kernel backports and package maintainer advisories.
Exploitation context
The source bundle marks CISA KEV as false and provides no evidence of active exploitation. The described attack requires local code execution by an unprivileged user and aims at kernel memory exhaustion through repeated triggering of the error path.
Researcher notes
The supplied record names the inadvertently fixing commit a71874379ec8 and two stable references. Version data in the bundle is not enough to map every distribution kernel, so validation should rely on vendor backports and source-level confirmation.
Mitigation direction
Update to a kernel build containing the referenced stable fix or vendor backport.
Check Linux distribution advisories for CVE-2024-14027 package status.
Prioritize hosts running untrusted local users, CI jobs, containers, or shared shells.
If patching is delayed, reduce untrusted local access where operationally feasible.
Monitor affected hosts for unexplained kernel memory pressure or file object growth.
Validation and detection
Identify running kernel versions across Linux hosts.
Compare vendor package changelogs against CVE-2024-14027 and referenced stable commits.
Confirm fixed kernels include the fdput cleanup change for fremovexattr().
Review whether local untrusted users or workloads can execute on each host.
Track remediation evidence in vulnerability management records.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-14027 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 9, 2026, 15:51 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.