CVE-2026-46093

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 27, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

mm/vmalloc: take vmap_purge_lock in shrinker - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ec05f51f1e65bce95528543eb73fda56fd201d94
generic

mm/vmalloc: take vmap_purge_lock in shrinker - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/687ccdf582169cd680aeaf24cc953807c4cd4345
generic

mm/vmalloc: take vmap_purge_lock in shrinker - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/12f2341b4c235d5593a433abac201c1c6725787f

Vendor Advisories for CVE-2026-46093(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (134 versions)7.0.4-1

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 10× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 260 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 07:41 UTCEG score recompute
  3. 2026-09-14 07:41 UTCVendor advisory
  4. 2026-09-14 07:41 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-13 03:39 UTCOSV refresh
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 05:19 UTCEG score recompute
  23. 2026-08-25 05:19 UTCVendor advisory
  24. 2026-08-25 05:19 UTCGHSA enrichment
  25. 2026-08-23 15:02 UTCEG score recompute
Show 75 more
  1. 2026-08-23 15:02 UTCGHSA enrichment
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-21 20:36 UTCVendor advisory
  5. 2026-08-21 20:35 UTCGHSA enrichment
  6. 2026-08-21 01:38 UTCEG score recompute
  7. 2026-08-21 01:38 UTCVendor advisory
  8. 2026-08-21 01:38 UTCGHSA enrichment
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 11:20 UTCEG score recompute
  11. 2026-08-20 11:20 UTCVendor advisory
  12. 2026-08-20 11:20 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 09:17 UTCVendor advisory
  17. 2026-08-17 09:17 UTCGHSA enrichment
  18. 2026-08-16 15:30 UTCEG score recompute
  19. 2026-08-16 15:30 UTCVendor advisory
  20. 2026-08-16 15:30 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:50 UTCEG score recompute
  23. 2026-08-16 02:50 UTCVendor advisory
  24. 2026-08-16 02:50 UTCGHSA enrichment
  25. 2026-08-16 02:14 UTCEPSS rescore
  26. 2026-08-15 02:56 UTCEG score recompute
  27. 2026-08-15 02:56 UTCVendor advisory
  28. 2026-08-15 02:56 UTCGHSA enrichment
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-14 14:07 UTCVendor advisory
  31. 2026-08-14 14:07 UTCGHSA enrichment
  32. 2026-08-14 01:27 UTCEG score recompute
  33. 2026-08-14 01:27 UTCVendor advisory
  34. 2026-08-14 01:27 UTCGHSA enrichment
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 03:36 UTCVendor advisory
  37. 2026-08-13 03:36 UTCGHSA enrichment
  38. 2026-08-12 14:56 UTCEG score recompute
  39. 2026-08-12 14:56 UTCVendor advisory
  40. 2026-08-12 14:56 UTCGHSA enrichment
  41. 2026-08-12 13:51 UTCEPSS rescore
  42. 2026-08-12 02:16 UTCEG score recompute
  43. 2026-08-12 02:16 UTCVendor advisory
  44. 2026-08-12 02:16 UTCGHSA enrichment
  45. 2026-08-11 13:35 UTCVendor advisory
  46. 2026-08-11 13:35 UTCGHSA enrichment
  47. 2026-08-11 00:12 UTCEG score recompute
  48. 2026-08-11 00:12 UTCVendor advisory
  49. 2026-08-11 00:12 UTCGHSA enrichment
  50. 2026-08-11 00:00 UTCEPSS rescore
  51. 2026-08-10 11:27 UTCVendor advisory
  52. 2026-08-10 11:27 UTCGHSA enrichment
  53. 2026-08-09 22:44 UTCEG score recompute
  54. 2026-08-09 22:44 UTCVendor advisory
  55. 2026-08-09 22:44 UTCGHSA enrichment
  56. 2026-08-09 13:46 UTCEPSS rescore
  57. 2026-08-09 10:04 UTCVendor advisory
  58. 2026-08-09 10:04 UTCGHSA enrichment
  59. 2026-08-08 21:23 UTCEG score recompute
  60. 2026-08-08 21:23 UTCVendor advisory
  61. 2026-08-08 21:23 UTCGHSA enrichment
  62. 2026-08-08 16:37 UTCEPSS rescore
  63. 2026-08-08 05:26 UTCVendor advisory
  64. 2026-08-08 05:26 UTCGHSA enrichment
  65. 2026-08-07 16:45 UTCVendor advisory
  66. 2026-08-07 16:45 UTCGHSA enrichment
  67. 2026-08-07 04:05 UTCVendor advisory
  68. 2026-08-07 04:05 UTCGHSA enrichment
  69. 2026-08-06 15:18 UTCEG score recompute
  70. 2026-08-06 15:18 UTCVendor advisory
  71. 2026-08-06 15:18 UTCGHSA enrichment
  72. 2026-08-06 13:47 UTCEPSS rescore
  73. 2026-08-06 02:22 UTCEG score recompute
  74. 2026-08-06 02:22 UTCVendor advisory
  75. 2026-08-06 02:22 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-46093?
CVE-2026-46093 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: take vmappurgelock in shrinker decayvapool_node() can be invoked concurrently from two paths: purgevmaparea_lazy() when pools are being purged, and the shrinker via vmapnodeshrink_scan(). However, decayvapool_node() is…
When was CVE-2026-46093 disclosed?
CVE-2026-46093 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46093 actively exploited?
CVE-2026-46093 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-46093?
CVE-2026-46093 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46093?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46093, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46093

Explore →

Is Your Infrastructure Affected by CVE-2026-46093?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.