Vulnerability · Published May 8, 2026 · Assigned by Linux

CVE-2026-43344perf/x86/intel/uncore: Fix die ID init and look up bugs

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 2% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.1%top 98.3% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

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 packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-43344
Debian:13linux6.12.111-1DEBIAN-CVE-2026-43344
Debian:14linux6.19.14-1DEBIAN-CVE-2026-43344
Debian:12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-43344
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-43344
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-43344
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-43344
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-43344
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-43344
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-43344
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1006.6UBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-43344
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-43344
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43344
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43344
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-43344
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-43344
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-43344

Affected products (as reported)

VendorProductVersions
Linux Linux 9a7832ce3d920426a36cdd78eda4b3568d4d09e3 – before 4eb511275e37c580156e787baab5232aeb0bfea09a7832ce3d920426a36cdd78eda4b3568d4d09e3 – before 184870af0e73f8ea2577c751fa098681465249f29a7832ce3d920426a36cdd78eda4b3568d4d09e3 – before bdb35811ff41a1678620a407056b6372f350028a9a7832ce3d920426a36cdd78eda4b3568d4d09e3 – before c79ef3342632e71ac8612a2a1cc17ac84dd258b49a7832ce3d920426a36cdd78eda4b3568d4d09e3 – before 6a5dc3ee97581da2907fc7acd62853f07184de679a7832ce3d920426a36cdd78eda4b3568d4d09e3 – before a16d1ec4dd0cdcf689f324adde6067083bce9099
Linux Linux 5.12

References