SECUFOCUSNOW
Home›CVE index›CVE-2026-46093
Review reviewHigh

CVE-2026-46093

Linux Linux, linux kernel

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
7.8
EPSS
0.13%
2.91% percentile
CISA KEV
Not listed
Published
2026.05.27
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.13%
Technical severityCVSS 7.8

Vulnerability overview

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.

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 7679ba6b36dbb300b757b672d6a32a606499e14b < c15ff206ba78820bf2873d0c668a882e99f4b631, >= 7679ba6b36dbb300b757b672d6a32a606499e14b < 687ccdf582169cd680aeaf24cc953807c4cd4345, >= 7679ba6b36dbb300b757b672d6a32a606499e14b < 12f2341b4c235d5593a433abac201c1c6725787f, >= 7679ba6b36dbb300b757b672d6a32a606499e14b < ec05f51f1e65bce95528543eb73fda56fd201d94, >= 6.9, >= 6.9 < 6.18.27, >= 6.19 < 7.0.4
Fixed versions
6.18.27, 7.0.4

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available
CVE-2026-46093 — Linux Linux, linux kernel | SECUFOCUS NOW