CVE-2026-46029

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. a secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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

June 16, 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(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-07-11ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-11ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-07-11ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-07-11ubuntu

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.

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 14× 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 140 total refreshes for this CVE.

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

Related CVEs(same vendor)

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 June 16, 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-46029?
CVE-2026-46029 has a CVSS v3 base score of 7.0 (NVD).
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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs