CVE-2026-43344

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-08. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

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

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

perf/x86/intel/uncore: Fix die ID init and look up bugs

In snbep_pci2phy_map_init(), in the nr_node_ids > 8 path, uncore_device_to_die() may return -1 when all CPUs associated with the UBOX device are offline.

Remove the WARN_ON_ONCE(die_id == -1) check for two reasons:

  • The current code breaks out of the loop. This is incorrect because
pci_get_device() does not guarantee iteration in domain or bus order, so additional UBOX devices may be skipped during the scan.
  • Returning -EINVAL is incorrect, since marking offline buses with
die_id == -1 is expected and should not be treated as an error.

Separately, when NUMA is disabled on a NUMA-capable platform, pcibus_to_node() returns NUMA_NO_NODE, causing uncore_device_to_die() to return -1 for all PCI devices. As a result, spr_update_device_location(), used on Intel SPR and EMR, ignores the corresponding PMON units and does not add them to the RB tree.

Fix this by using uncore_pcibus_to_dieid(), which retrieves topology from the UBOX GIDNIDMAP register and works regardless of whether NUMA is enabled in Linux. This requires snbep_pci2phy_map_init() to be added in spr_uncore_pci_init().

Keep uncore_device_to_die() only for the nr_node_ids > 8 case, where NUMA is expected to be enabled.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
1.1%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 18, 2026

Advisory Details (2)

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

perf/x86/intel/uncore: Fix die ID init and look up bugs - kernel/git/stable/linux.git - Linux kernel stable tree

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

perf/x86/intel/uncore: Fix die ID init and look up bugs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a5dc3ee97581da2907fc7acd62853f07184de67

Vendor Advisories for CVE-2026-43344(2)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-43344?
CVE-2026-43344 is a medium vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel/uncore: Fix die ID init and look up bugs In snbeppci2phymapinit(), in the nrnode_ids > 8 path, uncoredeviceto_die() may return -1 when all CPUs associated with the UBOX device are offline. Remove the…
When was CVE-2026-43344 disclosed?
CVE-2026-43344 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43344 actively exploited?
CVE-2026-43344 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43344?
CVE-2026-43344 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43344?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43344, 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-43344

Explore →

Is Your Infrastructure Affected by CVE-2026-43344?

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