CVE-2026-46093: mm/vmalloc: take vmap_purge_lock in shrinker
In the Linux kernel, the following vulnerability has been resolved:
mm/vmalloc: take vmap_purge_lock in shrinker
decay_va_pool_node() can be invoked concurrently from two paths:
__purge_vmap_area_lazy() when pools are being purged, and the shrinker via
vmap_node_shrink_scan().
However, decay_va_pool_node() is not safe to run concurrently, and the
shrinker path currently lacks serialization, leading to races and possible
leaks.
Protect decay_va_pool_node() by taking vmap_purge_lock in the shrinker
path to ensure serialization with purge users.
Security readout for executives and security teams
Plain-English summary
CVE-2026-46093 is a Linux kernel race condition in vmalloc memory management. A local authenticated attacker may be able to trigger memory corruption-like consequences reflected by high confidentiality, integrity, and availability impact in CVSS. It is not listed as known exploited in KEV based on the provided data.
Executive priority
Treat as a high-priority kernel maintenance issue, especially on systems where untrusted or semi-trusted users can run code. There is no provided evidence of active exploitation, so prioritize rapid patch planning over emergency response unless your environment has high local-user exposure.
Technical view
decay_va_pool_node() can run concurrently through __purge_vmap_area_lazy() and the shrinker path vmap_node_shrink_scan(). The shrinker path lacked vmap_purge_lock serialization, creating races and possible leaks. Stable kernel fixes add locking around the shrinker path to serialize decay_va_pool_node() with purge users.
Likely exposure
Systems running affected Linux kernel versions or downstream vendor kernels containing the vulnerable vmalloc shrinker code may be exposed. The source bundle lists Linux kernel affected versions including 6.9, 6.12.96, 6.18.27, 7.0.4, and 7.1, but downstream distribution mapping must be confirmed with vendor advisories.
Exploitation context
The CVSS vector is local, low complexity, low privileges required, and no user interaction. The provided sources do not claim public exploitation or KEV listing. Practical impact depends on kernel configuration, workload, and whether an attacker has local code execution on the host.
Researcher notes
The core issue is missing serialization in vmap_node_shrink_scan() for decay_va_pool_node(). Analysis should focus on affected kernel lineage and whether vendor backports include the locking fix. The provided record does not include CWE mapping, exploit availability, or distribution-specific fixed package versions.
Mitigation direction
Apply Linux stable kernel fixes referenced for CVE-2026-46093 when available for your branch.
Check your Linux distribution or appliance vendor advisory for backported fixed kernel packages.
Prioritize shared servers, multi-user systems, containers hosts, and internet-facing systems allowing local workloads.
If no vendor package exists, evaluate upgrading to a fixed upstream stable kernel.
Validation and detection
Inventory Linux kernel versions across servers, images, appliances, and container hosts.
Compare running kernels against vendor advisories and the referenced upstream stable commits.
Confirm patched kernels include the vmap_purge_lock change in the shrinker path.
After remediation, verify systems booted into the updated kernel, not only installed it.
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-2026-46093 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.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
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.