perf tools: Use perf_env__get_cpu_topology() in machine__resolve() (CVE-2026-80670) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80670

perf tools: Use perf_env__get_cpu_topology() in machine__resolve()

Answer in brief

CVE-2026-80670 records a Unknown severity vulnerability in perf tools: Use perf_env__get_cpu_topology() in machine__resolve(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 28, 2026Updated Aug 28, 2026Source checked Aug 28, 2026First seen by HOL Aug 28, 2026Material review Aug 28, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=0c4c4debb0adda4c18c158d95031dc2b9f637869 <b9e8406651dcc1c19238aad11861a758683525b4 \|\| >=0c4c4debb0adda4c18c158d95031dc2b9f637869 <eb266a14c16a93eb4db7b56a452d6be93f8bdcd4 \|\| >=0c4c4debb0adda4c18c158d95031dc2b9f637869 <5484b43a0ec8231c36fba6ead654cb72dbba8b8f	b9e8406651dcc1c19238aad11861a758683525b4, eb266a14c16a93eb4db7b56a452d6be93f8bdcd4, 5484b43a0ec8231c36fba6ead654cb72dbba8b8f
Linux/Linuxgeneric	4.4	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to b9e8406651dcc1c19238aad11861a758683525b4 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 28, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.