CVE-2026-90046

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

mm/page_alloc: don't spin_trylock() in NMI on UP

Patch series "mm/page_alloc: fixes for free_pages_nolock() on RT/UP".

Pre-existing bugs found by Sashiko during review of this other series: https://lore.kernel.org/all/[email protected]/

I have not reproduced these bugs, and I suspect there is no real-world user that is affected by them.

This patch (of 2):

As noted in can_spin_trylock(), using this is unsafe in this context. commit 620b46ed6ae17 ("mm/page_alloc: return NULL early from alloc_frozen_pages_nolock() in NMI on UP") fixed this on the alloc side but missed the free side.

Impact: If BPF programs using these features in NMI (probably tracing) are present on non-SMP builds this might crash the kernel and is probably exploitable by local attackers for privilege escalation.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 16, 2026

Last Modified

September 28, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

mm/page_alloc: don't spin_trylock() in NMI on UP - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/68a069b407303e71db371df85036101e8ff59280
generic

mm/page_alloc: don't spin_trylock() in NMI on UP - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3105ae628fb785d48b49256468be4f21a7b3cfc0
generic

mm/page_alloc: don't spin_trylock() in NMI on UP - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06c76d3c389ff504052f64b1acee44651bd847fa

Vendor Advisories for CVE-2026-90046(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (177 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 26× in last 7d / 77× 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.

  1. 2026-10-05 06:12 UTCEG score recompute
  2. 2026-10-05 06:12 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 17:42 UTCGHSA enrichment
  5. 2026-10-04 05:07 UTCGHSA enrichment
  6. 2026-10-03 16:38 UTCGHSA enrichment
  7. 2026-10-03 04:10 UTCEG score recompute
  8. 2026-10-03 04:10 UTCGHSA enrichment
  9. 2026-10-02 15:41 UTCGHSA enrichment
  10. 2026-10-02 03:12 UTCEG score recompute
  11. 2026-10-02 03:12 UTCGHSA enrichment
  12. 2026-10-01 19:51 UTCEPSS rescore
  13. 2026-10-01 14:34 UTCGHSA enrichment
  14. 2026-10-01 02:06 UTCEG score recompute
  15. 2026-10-01 02:05 UTCGHSA enrichment
  16. 2026-09-30 15:04 UTCEPSS rescore
  17. 2026-09-30 13:27 UTCGHSA enrichment
  18. 2026-09-30 00:53 UTCEG score recompute
  19. 2026-09-30 00:53 UTCGHSA enrichment
  20. 2026-09-29 11:46 UTCGHSA enrichment
  21. 2026-09-28 23:15 UTCEG score recompute
  22. 2026-09-28 23:15 UTCGHSA enrichment
  23. 2026-09-28 15:23 UTCEG score recompute
  24. 2026-09-28 15:23 UTCGHSA enrichment
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 52 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 02:52 UTCGHSA enrichment
  3. 2026-09-27 14:23 UTCEG score recompute
  4. 2026-09-27 14:23 UTCGHSA enrichment
  5. 2026-09-27 13:49 UTCEPSS rescore
  6. 2026-09-27 01:55 UTCEG score recompute
  7. 2026-09-27 01:54 UTCGHSA enrichment
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-26 13:21 UTCGHSA enrichment
  10. 2026-09-26 00:48 UTCEG score recompute
  11. 2026-09-26 00:48 UTCGHSA enrichment
  12. 2026-09-25 11:52 UTCGHSA enrichment
  13. 2026-09-24 23:23 UTCEG score recompute
  14. 2026-09-24 23:23 UTCGHSA enrichment
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-24 10:54 UTCGHSA enrichment
  17. 2026-09-23 22:25 UTCEG score recompute
  18. 2026-09-23 22:25 UTCGHSA enrichment
  19. 2026-09-23 17:54 UTCEPSS rescore
  20. 2026-09-23 09:56 UTCGHSA enrichment
  21. 2026-09-22 21:27 UTCEG score recompute
  22. 2026-09-22 21:27 UTCGHSA enrichment
  23. 2026-09-22 16:01 UTCEPSS rescore
  24. 2026-09-22 08:59 UTCEG score recompute
  25. 2026-09-22 08:58 UTCGHSA enrichment
  26. 2026-09-21 21:09 UTCEPSS rescore
  27. 2026-09-21 20:26 UTCGHSA enrichment
  28. 2026-09-21 07:49 UTCEG score recompute
  29. 2026-09-21 07:49 UTCGHSA enrichment
  30. 2026-09-20 20:16 UTCEPSS rescore
  31. 2026-09-20 19:20 UTCGHSA enrichment
  32. 2026-09-20 06:50 UTCGHSA enrichment
  33. 2026-09-19 18:17 UTCEG score recompute
  34. 2026-09-19 18:17 UTCGHSA enrichment
  35. 2026-09-19 05:48 UTCEG score recompute
  36. 2026-09-19 05:48 UTCGHSA enrichment
  37. 2026-09-18 19:28 UTCEPSS rescore
  38. 2026-09-18 17:17 UTCGHSA enrichment
  39. 2026-09-18 04:48 UTCEG score recompute
  40. 2026-09-18 04:48 UTCGHSA enrichment
  41. 2026-09-17 19:32 UTCEPSS rescore
  42. 2026-09-17 16:19 UTCGHSA enrichment
  43. 2026-09-17 03:50 UTCEG score recompute
  44. 2026-09-17 03:50 UTCGHSA enrichment
  45. 2026-09-16 15:21 UTCEG score recompute
  46. 2026-09-16 15:21 UTCGHSA enrichment
  47. 2026-09-16 14:46 UTCEG score recompute▲ 7.80
  48. 2026-09-16 14:46 UTCGHSA enrichment
  49. 2026-09-16 14:45 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  50. 2026-09-16 11:21 UTCNVD update
  51. 2026-09-16 10:36 UTCEG score recompute
  52. 2026-09-16 10:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-90046?
CVE-2026-90046 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/pagealloc: don't spintrylock() in NMI on UP Patch series "mm/pagealloc: fixes for freepages_nolock() on RT/UP". Pre-existing bugs found by Sashiko during review of this other series:…
When was CVE-2026-90046 disclosed?
CVE-2026-90046 was first published on September 16, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90046 actively exploited?
CVE-2026-90046 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90046?
CVE-2026-90046 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90046?
No fix for CVE-2026-90046 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90046 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-90046?

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

Book a Demo →Browse All CVEs