CVE-2026-80670
CriticalIn the Linux kernel, the following vulnerability has been resolved: perf tools: Use perf_env__get_cpu_topology() in machine__resolve() machine__resolve() accesses env->cpu[al->cpu].socket_id after checking al->cpu >= 0 and env->cpu != NULL, but without validating al->cpu against env->nr_cpus_avail. Since al->cpu comes from the untrusted perf.data sample, a crafted file with a large CPU index causes an out-of-bounds heap read. Use perf_env__get_cpu_topology() which validates both NULL and bounds. Also bounds-check al->cpu before the cast to struct perf_cpu (int16_t): without this, values like 65536 silently truncate to 0, bypassing the accessor's internal check and returning CPU 0's topology.
CVSS 3.1 score
9.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Affected versions
Linux kernel versions
4.4
and later are affected. Fixed in
6.18.40,
7.1.5,
7.2
and their respective stable series.
References
3 totalFrequently asked questions
-
What is CVE-2026-80670?
CVE-2026-80670 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.1 out of 10 . It affects Linux kernel versions from 4.4 onward and has been patched in 6.18.40, 7.1.5 and 7.2. CVE-2026-80670 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2026-80670?
CVE-2026-80670 has a CVSS score of 9.1 out of 10, rated Critical severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H. -
Is there a patch available for CVE-2026-80670?
Yes. CVE-2026-80670 has been patched. Fixed versions include 6.18.40, 7.1.5 and 7.2. If you are running Linux kernel 4.4 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-80670 actively exploited?
No. CVE-2026-80670 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.