CVE-2026-43212

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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:

LoongArch: Make cpumask_of_node() robust against NUMA_NO_NODE

The arch definition of cpumask_of_node() cannot handle NUMA_NO_NODE - which is a valid index - so add a check for this.

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
4%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

LoongArch: Make cpumask_of_node() robust against NUMA_NO_NODE - kernel/git/stable/linux.git - Linux kernel stable tree

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

LoongArch: Make cpumask_of_node() robust against NUMA_NO_NODE - kernel/git/stable/linux.git - Linux kernel stable tree

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

LoongArch: Make cpumask_of_node() robust against NUMA_NO_NODE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/94b0c831eda778ae9e4f2164a8b3de485d8977bb
generic

LoongArch: Make cpumask_of_node() robust against NUMA_NO_NODE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92adfb707beec0fe956424373654a70aad35ea13
generic

LoongArch: Make cpumask_of_node() robust against NUMA_NO_NODE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61a56df2fbaad3a4d00f0c6a904b5d1ee8982eb4
generic

LoongArch: Make cpumask_of_node() robust against NUMA_NO_NODE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d8f2f024801019d85159a020b72a4424b46bcf4

Patch Availability(11)

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
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1

All Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 7× in last 7d / 31× 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 208 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43212?
CVE-2026-43212 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: LoongArch: Make cpumaskofnode() robust against NUMANONODE The arch definition of cpumaskofnode() cannot handle NUMANONODE - which is a valid index - so add a check for this.
When was CVE-2026-43212 disclosed?
CVE-2026-43212 was first published in the National Vulnerability Database on May 6, 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-43212 actively exploited?
CVE-2026-43212 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 96.4% of all scored CVEs.
What is the CVSS score of CVE-2026-43212?
CVE-2026-43212 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43212?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43212, 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-43212

Explore →

Is Your Infrastructure Affected by CVE-2026-43212?

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