CVE-2026-43344

published 8 May 2026 · updated 16 Nov 2026

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

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.19.14, Kernel 4eb511275e37c580156e787baab5232aeb0bfea0, Kernel 6a5dc3ee97581da2907fc7acd62853f07184de67 and 8 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=5.12 <6.19.14, =7.0, >=9a7832ce3d920426a36cdd78eda4b3568d4d09e3 <4eb511275e37c580156e787baab5232aeb0bfea0, >=9a7832ce3d920426a36cdd78eda4b3568d4d09e3 <6a5dc3ee97581da2907fc7acd62853f07184de67, >=9a7832ce3d920426a36cdd78eda4b3568d4d09e3 <a16d1ec4dd0cdcf689f324adde6067083bce9099, >=9a7832ce3d920426a36cdd78eda4b3568d4d09e3 <bdb35811ff41a1678620a407056b6372f350028a, >=9a7832ce3d920426a36cdd78eda4b3568d4d09e3 <c79ef3342632e71ac8612a2a1cc17ac84dd258b4, =5.12, >=9a7832ce3d920426a36cdd78eda4b3568d4d09e3 <184870af0e73f8ea2577c751fa098681465249f26.19.14, 4eb511275e37c580156e787baab5232aeb0bfea0, 6a5dc3ee97581da2907fc7acd62853f07184de67, a16d1ec4dd0cdcf689f324adde6067083bce9099, bdb35811ff41a1678620a407056b6372f350028a, c79ef3342632e71ac8612a2a1cc17ac84dd258b4, 184870af0e73f8ea2577c751fa098681465249f2
linux-kernel: Kernel>=5.12.0 <6.1.191, >=6.13.0 <6.18.50, >=6.19.0 <6.19.14, >=6.2.0 <6.6.157, >=6.7.0 <6.12.1096.1.191, 6.18.50, 6.19.14, 6.6.157, 6.12.109

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-43344 severity on Zeptric[![CVE-2026-43344](https://zeptric.io/badge/cve/CVE-2026-43344.svg)](https://zeptric.io/cve/CVE-2026-43344)