CVE-2026-43344 (GCVE-0-2026-43344)
Vulnerability from cvelistv5 – Published: 2026-05-08 13:39 – Updated: 2026-05-08 13:39
VLAI?
Title
perf/x86/intel/uncore: Fix die ID init and look up bugs
Summary
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.
Severity ?
No CVSS data available.
Assigner
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"arch/x86/events/intel/uncore.c",
"arch/x86/events/intel/uncore_snbep.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "6a5dc3ee97581da2907fc7acd62853f07184de67",
"status": "affected",
"version": "9a7832ce3d920426a36cdd78eda4b3568d4d09e3",
"versionType": "git"
},
{
"lessThan": "a16d1ec4dd0cdcf689f324adde6067083bce9099",
"status": "affected",
"version": "9a7832ce3d920426a36cdd78eda4b3568d4d09e3",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/x86/events/intel/uncore.c",
"arch/x86/events/intel/uncore_snbep.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.12"
},
{
"lessThan": "5.12",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.19.*",
"status": "unaffected",
"version": "6.19.14",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.0",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19.14",
"versionStartIncluding": "5.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0",
"versionStartIncluding": "5.12",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel/uncore: Fix die ID init and look up bugs\n\nIn snbep_pci2phy_map_init(), in the nr_node_ids \u003e 8 path,\nuncore_device_to_die() may return -1 when all CPUs associated\nwith the UBOX device are offline.\n\nRemove the WARN_ON_ONCE(die_id == -1) check for two reasons:\n\n- The current code breaks out of the loop. This is incorrect because\n pci_get_device() does not guarantee iteration in domain or bus order,\n so additional UBOX devices may be skipped during the scan.\n\n- Returning -EINVAL is incorrect, since marking offline buses with\n die_id == -1 is expected and should not be treated as an error.\n\nSeparately, when NUMA is disabled on a NUMA-capable platform,\npcibus_to_node() returns NUMA_NO_NODE, causing uncore_device_to_die()\nto return -1 for all PCI devices. As a result,\nspr_update_device_location(), used on Intel SPR and EMR, ignores the\ncorresponding PMON units and does not add them to the RB tree.\n\nFix this by using uncore_pcibus_to_dieid(), which retrieves topology\nfrom the UBOX GIDNIDMAP register and works regardless of whether NUMA\nis enabled in Linux. This requires snbep_pci2phy_map_init() to be\nadded in spr_uncore_pci_init().\n\nKeep uncore_device_to_die() only for the nr_node_ids \u003e 8 case, where\nNUMA is expected to be enabled."
}
],
"providerMetadata": {
"dateUpdated": "2026-05-08T13:39:30.537Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/6a5dc3ee97581da2907fc7acd62853f07184de67"
},
{
"url": "https://git.kernel.org/stable/c/a16d1ec4dd0cdcf689f324adde6067083bce9099"
}
],
"title": "perf/x86/intel/uncore: Fix die ID init and look up bugs",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-43344",
"datePublished": "2026-05-08T13:39:30.537Z",
"dateReserved": "2026-05-01T14:12:56.003Z",
"dateUpdated": "2026-05-08T13:39:30.537Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-43344",
"date": "2026-05-09",
"epss": "0.00018",
"percentile": "0.05073"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-43344\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-05-08T14:16:44.433\",\"lastModified\":\"2026-05-08T14:16:44.433\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nperf/x86/intel/uncore: Fix die ID init and look up bugs\\n\\nIn snbep_pci2phy_map_init(), in the nr_node_ids \u003e 8 path,\\nuncore_device_to_die() may return -1 when all CPUs associated\\nwith the UBOX device are offline.\\n\\nRemove the WARN_ON_ONCE(die_id == -1) check for two reasons:\\n\\n- The current code breaks out of the loop. This is incorrect because\\n pci_get_device() does not guarantee iteration in domain or bus order,\\n so additional UBOX devices may be skipped during the scan.\\n\\n- Returning -EINVAL is incorrect, since marking offline buses with\\n die_id == -1 is expected and should not be treated as an error.\\n\\nSeparately, when NUMA is disabled on a NUMA-capable platform,\\npcibus_to_node() returns NUMA_NO_NODE, causing uncore_device_to_die()\\nto return -1 for all PCI devices. As a result,\\nspr_update_device_location(), used on Intel SPR and EMR, ignores the\\ncorresponding PMON units and does not add them to the RB tree.\\n\\nFix this by using uncore_pcibus_to_dieid(), which retrieves topology\\nfrom the UBOX GIDNIDMAP register and works regardless of whether NUMA\\nis enabled in Linux. This requires snbep_pci2phy_map_init() to be\\nadded in spr_uncore_pci_init().\\n\\nKeep uncore_device_to_die() only for the nr_node_ids \u003e 8 case, where\\nNUMA is expected to be enabled.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/6a5dc3ee97581da2907fc7acd62853f07184de67\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/a16d1ec4dd0cdcf689f324adde6067083bce9099\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…