CVE-2026-43079
perf/x86/intel/uncore Array Overflow in Linux Kernel
Publication date: 2026-05-06
Last updated on: 2026-05-06
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's perf subsystem for Intel uncore performance monitoring. Specifically, when NUMA is disabled and the system boots with fewer CPUs than expected in die 0, the discovery table for offline dies is still parsed.
Because the discovery table continues to be parsed even if all CPUs in a die are offline, it can lead to an array overflow at the code location pmu->boxes[die] = box in the function uncore_pci_pmu_register().
This overflow can trigger warnings or potentially cause other issues related to system stability or security.
How can this vulnerability impact me? :
The vulnerability can cause an array overflow in the Linux kernel's performance monitoring code, which may trigger system warnings or lead to other unspecified issues.
Such an overflow could potentially affect system stability or reliability, possibly causing crashes or unexpected behavior.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing specific kernel warning messages related to the intel_uncore module. In particular, the warning message "WARNING: CPU: <number> PID: <number> at uncore.c:1157 uncore_pci_pmu_register+0x136/0x160 [intel_uncore]" indicates the issue.
To detect this on your system, you can check the kernel logs for such warnings using commands like:
- dmesg | grep -i 'uncore_pci_pmu_register'
- journalctl -k | grep -i 'uncore_pci_pmu_register'
- grep -i 'uncore_pci_pmu_register' /var/log/kern.log
These commands search for the warning message in kernel logs, which can help identify if the vulnerability is present due to the array overflow condition triggered when CPUs in a die are offline.