CVE-2026-80670

Received Received - Intake

Out-of-Bounds Read in Linux Kernel perf Tools

Publication date: 2026-08-28

Last updated on: 2026-08-29

Assigner: kernel.org

Description

In 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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-28

Last Modified

2026-08-29

Generated

2026-09-17

AI Q&A

2026-08-28

EPSS Evaluated

2026-09-15

NVD

CVE-2026-80670

EUVD

EUVD-2026-67546

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This is a vulnerability in the Linux kernel's perf tools. It involves an out-of-bounds heap read in machine__resolve() due to missing validation of the CPU index from untrusted perf.data samples. The issue arises when a crafted file uses a large CPU index, bypassing checks and accessing invalid memory.

Detection Guidance

This vulnerability is specific to perf tools in the Linux kernel and requires examining perf.data files or kernel traces. Check for out-of-bounds CPU index values in perf.data files using perf tools commands like 'perf report' or 'perf script'. Inspect kernel logs for crashes or heap corruption related to perf events.

Impact Analysis

An attacker could exploit this to cause a denial-of-service (DoS) or potentially execute arbitrary code on systems running vulnerable Linux kernels. It requires a crafted perf.data file, which could be delivered via malicious input or files.

Compliance Impact

This vulnerability could lead to unauthorized access or data breaches, violating confidentiality requirements in GDPR and HIPAA. Organizations must patch systems to maintain compliance with these regulations.

Mitigation Strategies

Update the Linux kernel to a patched version that includes the fix for CVE-2026-80670. Avoid using perf tools on untrusted perf.data files until the system is updated. Monitor kernel logs for signs of exploitation attempts.

Hi! I’m here to help you understand CVE-2026-80670. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70