CVE-2026-43344

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

MEDIUM
5.5
CVSS Score
Published: May 8, 2026 at 01:39 PM UTC
Updated: September 14, 2026 at 12:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.12 ≤ v < 6.12.1095.12 ≤ v < 6.18.505.12 ≤ v < 6.19.145.12 ≤ v < 6.6.1575.12 ≤ v < 7.07.0 rc17.0 rc27.0 rc37.0 rc47.0 rc57.0 rc67.0 rc79a7832ce3d920426a36cdd78eda4b3568d4d09e3
Vendor states this is fixed in 184870af0e73f8ea2577c751fa098681465249f2 (fixed)
Vendor states this is fixed in 6a5dc3ee97581da2907fc7acd62853f07184de67 (fixed)
Vendor states this is fixed in a16d1ec4dd0cdcf689f324adde6067083bce9099 (fixed)
Vendor states this is fixed in bdb35811ff41a1678620a407056b6372f350028a (fixed)
Vendor states this is fixed in c79ef3342632e71ac8612a2a1cc17ac84dd258b4 (fixed)
Vendor states this is fixed in 5.12 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.19.14 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-617

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card