CVE-2026-43344 Details
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.
A vulnerability in the Linux kernel's handling of uncore die IDs has been addressed. The issue arose in the 'snbep_pci2phy_map_init()' function, specifically when the number of node IDs exceeded eight. In this scenario, the 'uncore_device_to_die()' function could incorrectly return -1 if all CPUs linked to the UBOX device were offline. This mismanagement was due to a WARN_ON_ONCE check that disrupted the device scanning process, potentially causing the omission of other UBOX devices. Additionally, when NUMA was disabled on platforms that supported it, the 'pcibus_to_node()' function would return 'Numa_NO_NODE', leading 'uncore_device_to_die()' to fail for all PCI devices. Consequently, the 'spr_update_device_location()' function, relevant for Intel SPR and EMR, overlooked certain PMON units. The vulnerability has been fixed by modifying the die ID retrieval process to rely on the UBOX GIDNIDMAP register, ensuring accurate topology mapping regardless of NUMA settings. This adjustment required integrating the 'snbep_pci2phy_map_init()' function into the 'spr_uncore_pci_init()' routine, while retaining the original 'uncore_device_to_die()' function only for cases with more than eight node IDs, where NUMA is expected to be active.
Users can apply the latest patches from the Linux kernel stable tree to address this vulnerability. The specific commit containing the fix can be downloaded as a tarball.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-617 | Reachable Assertion | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.12, < 6.19.14 7.0 rc1 7.0 rc2 7.0 rc3 7.0 rc4 7.0 rc5 7.0 rc6 7.0 rc7 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 14, 2026 | CVE Modified | kernel.org |
| Sep 7, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 18, 2026 | Initial Analysis | [email protected] |
| May 8, 2026 | New CVE Received | kernel.org |