CVE-2026-43344: Linux kernel · perf/x86/intel/uncore: Fix die ID init and look up bugs
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c79ef3342632e71ac8612a2a1cc17ac84dd258b4 : update Linux kernel when convenient.
Data as of 30 Oct 2026, 12:49 UTC
Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- Patch
- Available – fixed in c79ef3342632e71ac8612a2a1cc17ac84dd258b4, bdb35811ff41a1678620a407056b6372f350028a, a16d1ec4dd0cdcf689f324adde6067083bce9099 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel commits identified by the fixedVersions hashes. Users and administrators should update their Linux kernel to a version including these fixes to resolve the die ID initialization and lookup bugs in the perf subsystem. No additional mitigation actions are required beyond applying the official patch.
Description
CVE-2026-43344 addresses a flaw in the Linux kernel's perf subsystem related to Intel uncore device die ID initialization and lookup. The issue occurs in the snbep_pci2phy_map_init() function when handling more than eight node IDs, where uncore_device_to_die() may return -1 if all CPUs associated with a UBOX device are offline. This caused incorrect error handling and skipping of devices during scanning. Additionally, when NUMA is disabled on NUMA-capable platforms, the existing method failed to correctly identify device locations, leading to some PMON units being ignored. The fix involves removing improper error checks and using a more reliable method to retrieve topology information regardless of NUMA status.
References
- git.kernel.org/stable/c/4eb511275e37c580156e787baab5232aeb0bfea0 (opens in a new tab)
- git.kernel.org/stable/c/184870af0e73f8ea2577c751fa098681465249f2 (opens in a new tab)
- git.kernel.org/stable/c/bdb35811ff41a1678620a407056b6372f350028a (opens in a new tab)
- git.kernel.org/stable/c/c79ef3342632e71ac8612a2a1cc17ac84dd258b4 (opens in a new tab)
- git.kernel.org/stable/c/6a5dc3ee97581da2907fc7acd62853f07184de67 (opens in a new tab)
- git.kernel.org/stable/c/a16d1ec4dd0cdcf689f324adde6067083bce9099 (opens in a new tab)