Linux hwe edge: 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… (CVE-2026-46093)
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.
AI Analysis
Technical Summary
CVE-2026-46093 addresses a concurrency issue in the Linux kernel's vmalloc subsystem. The function decay_va_pool_node() can be called concurrently from __purge_vmap_area_lazy() during pool purging and from the shrinker via vmap_node_shrink_scan(). Since decay_va_pool_node() is not safe for concurrent execution and the shrinker path lacked serialization, this led to race conditions and possible memory leaks. The vulnerability is mitigated by acquiring the vmap_purge_lock in the shrinker path to serialize access and prevent races.
Potential Impact
The vulnerability allows concurrent execution of a non-thread-safe function, causing race conditions that can lead to memory leaks and potentially compromise system stability or security. The CVSS vector indicates high impact on confidentiality, integrity, and availability, meaning exploitation could result in significant system compromise.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description indicates that a fix involves taking the vmap_purge_lock in the shrinker path to ensure serialization. Users should monitor official Linux kernel advisories for patches addressing CVE-2026-46093 and apply them promptly once available.
Linux hwe edge: 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… (CVE-2026-46093)
Description
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.
CVSS v3.1
Score 7.8high
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-46093 addresses a concurrency issue in the Linux kernel's vmalloc subsystem. The function decay_va_pool_node() can be called concurrently from __purge_vmap_area_lazy() during pool purging and from the shrinker via vmap_node_shrink_scan(). Since decay_va_pool_node() is not safe for concurrent execution and the shrinker path lacked serialization, this led to race conditions and possible memory leaks. The vulnerability is mitigated by acquiring the vmap_purge_lock in the shrinker path to serialize access and prevent races.
Potential Impact
The vulnerability allows concurrent execution of a non-thread-safe function, causing race conditions that can lead to memory leaks and potentially compromise system stability or security. The CVSS vector indicates high impact on confidentiality, integrity, and availability, meaning exploitation could result in significant system compromise.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description indicates that a fix involves taking the vmap_purge_lock in the shrinker path to ensure serialization. Users should monitor official Linux kernel advisories for patches addressing CVE-2026-46093 and apply them promptly once available.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-vf24-gv7c-563r
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-46093"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a5bd3182a4a8d5989284fc3
Added to database: 07/18/2026, 19:25:12 UTC
Last enriched: 07/18/2026, 19:26:26 UTC
Last updated: 07/31/2026, 19:30:22 UTC
Views: 43
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.