CVE-2026-46029

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 5 sources updated this week
7.0EG
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.0Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

mm/slab: return NULL early from kmalloc_nolock() in NMI on UP

On UP kernels (!CONFIG_SMP), spin_trylock() is a no-op that unconditionally succeeds even when the lock is already held. As a result, kmalloc_nolock() called from NMI context can re-enter the slab allocator and acquire n->list_lock that the interrupted context is already holding, corrupting slab state.

With CONFIG_DEBUG_SPINLOCK on UP, the following BUG is triggered with the slub_kunit test module:

BUG: spinlock trylock failure on UP on CPU#0, kunit_try_catch/243 [...] Call Trace: dump_stack_lvl+0x3f/0x60 do_raw_spin_trylock+0x41/0x50 _raw_spin_trylock+0x24/0x50 get_from_partial_node+0x120/0x4d0 ___slab_alloc+0x8a/0x4c0 kmalloc_nolock_noprof+0x164/0x310 [...]

Fix this by returning NULL early when invoked from NMI on a UP kernel.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

May 27, 2026

Last Modified

August 5, 2026

Advisory Details (3)

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

mm/slab: return NULL early from kmalloc_nolock() in NMI on UP - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/slab: return NULL early from kmalloc_nolock() in NMI on UP - kernel/git/stable/linux.git - Linux kernel stable tree

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

mm/slab: return NULL early from kmalloc_nolock() in NMI on UP - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5b31044e649e3e54c2caef135c09b371c2fbcd08

Vendor Advisories for CVE-2026-46029(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

(1 across 1 ecosystem)
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 9× in last 7d / 41× 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 259 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46029?
CVE-2026-46029 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/slab: return NULL early from kmalloc_nolock() in NMI on UP On UP kernels (!CONFIGSMP), spintrylock() is a no-op that unconditionally succeeds even when the lock is already held. As a result, kmalloc_nolock() called from NMI…
When was CVE-2026-46029 disclosed?
CVE-2026-46029 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-46029 actively exploited?
CVE-2026-46029 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 95.7% of all scored CVEs.
What is the CVSS score of CVE-2026-46029?
CVE-2026-46029 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46029?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46029, 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-46029

Explore →

Is Your Infrastructure Affected by CVE-2026-46029?

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