CVE-2024-47668: lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()
In the Linux kernel, the following vulnerability has been resolved:
lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()
If we need to increase the tree depth, allocate a new node, and then
race with another thread that increased the tree depth before us, we'll
still have a preallocated node that might be used later.
If we then use that node for a new non-root node, it'll still have a
pointer to the old root instead of being zeroed - fix this by zeroing it
in the cmpxchg failure path.
Security readout for executives and security teams
Plain-English summary
A rare Linux kernel timing flaw can reuse an internal tree node containing an outdated pointer. A local, low-privileged user may be able to trigger serious confidentiality, integrity, or availability impact, although the supplied sources do not demonstrate a working exploit or confirmed attacks.
Executive priority
Treat as a high-priority kernel maintenance issue where untrusted users or workloads can run locally. Accelerate remediation on shared infrastructure and sensitive systems. For tightly controlled single-purpose hosts, schedule prompt vendor-approved updates while recognizing that the reported race is rare and exploitation is not confirmed.
Technical view
During generic radix-tree growth, two threads can race after allocating replacement nodes. If cmpxchg loses the race, the unused node may retain a pointer to the former root. Later reuse as a non-root node can leave the tree in an unsafe state. The kernel fix zeroes that node on the cmpxchg failure path.
Likely exposure
Potential exposure includes Linux systems running the affected versions or derived kernels, particularly multi-user systems, shared compute, containers, and other environments permitting local untrusted code. Exact exposure depends on distribution backports and whether relevant generic radix-tree operations can be reached; version strings alone may be misleading.
Exploitation context
The CVSS vector describes local access, low privileges, low complexity, and no user interaction, with potentially high impact across confidentiality, integrity, and availability. The source bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit.
Researcher notes
No CWE is assigned in the supplied record. The affected-version data is unusual, including duplicate commit identifiers and mixed release entries, so validate each vendor kernel by backport status. The evidence establishes a stale-pointer race and its fix, but does not establish a reliable exploitation primitive, privilege escalation, or observed attacks.
Mitigation direction
Install a vendor-supported kernel containing the applicable stable fix or distribution backport.
Prioritize multi-user hosts and systems that execute code from untrusted tenants or containers.
Restrict unnecessary local accounts and untrusted workload execution until kernels are updated.
Reboot into the corrected kernel after installation, following vendor operational guidance.
Validation and detection
Inventory running kernel versions across hosts, images, appliances, and recovery environments.
Check distribution advisories and package changelogs for a CVE-2024-47668 backport.
Confirm the running kernel includes the applicable stable commit, not merely an installed package.
Verify hosts rebooted successfully and now run the corrected kernel.
Review local-access controls and identify systems executing untrusted or tenant-supplied workloads.
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-47668 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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.