LiveActive security incident?Get immediate response
CVE Record

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

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.

CriticalCVSS 9.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Linux perf tools can read beyond allocated memory when analyzing a maliciously crafted perf.data file containing an invalid CPU index. This may expose process memory or disrupt analysis. The supplied record rates it critical, but practical exposure depends on whether untrusted perf.data files reach vulnerable perf tooling.

Executive priority

Treat as an urgent patching and exposure-review item for shared diagnostics, support portals, CI systems, and analysis services handling outside perf.data. Other systems should follow normal expedited remediation after confirming package applicability. There is no supplied evidence of active exploitation.

Technical view

machine__resolve() used a sample-controlled CPU index without checking it against env->nr_cpus_avail. Large values caused an out-of-bounds heap read; some values could also truncate during an int16_t cast and bypass validation. The referenced fix uses perf_env__get_cpu_topology() and validates the index before casting.

Likely exposure

Prioritize systems where Linux perf tools ingest perf.data supplied by users, customers, automation, or external diagnostic workflows. The supplied affected-version data is ambiguous and should not be treated as a reliable range without vendor confirmation. Systems that never process untrusted perf.data have lower practical exposure.

Exploitation context

The bundle reports no CISA KEV listing and provides no evidence of active exploitation or a public exploit. Exploitation requires a crafted perf.data sample to be processed by affected tooling. Although the supplied CVSS vector says network-accessible and no interaction, the description alone does not establish a direct remote attack path.

Researcher notes

The defect is an out-of-bounds heap read in perf tooling, not described as a kernel privilege-escalation flaw. A second validation issue arises because large integers may truncate to int16_t before accessor checks. The reported CVSS impacts confidentiality and availability, not integrity. Exact affected-version boundaries remain unclear in the supplied data.

Mitigation direction

  • Update Linux perf packages to vendor-supported builds containing the referenced bounds-check fix.
  • Restrict perf.data ingestion to trusted sources until affected builds are updated.
  • Isolate analysis of externally supplied perf.data using least privilege and resource controls.
  • Check Linux distribution advisories for exact affected and fixed package versions.

Validation and detection

  • Inventory installed Linux perf package versions on systems that analyze perf.data.
  • Confirm whether the referenced fix commits were included or backported by the distributor.
  • Identify workflows accepting perf.data from untrusted or externally controlled sources.
  • After updating, verify package provenance and repeat normal perf.data processing tests.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-80670 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H3.95.2Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2026-80670Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0c4c4debb0adda4c18c158d95031dc2b9f637869, 0c4c4debb0adda4c18c158d95031dc2b9f637869, 0c4c4debb0adda4c18c158d95031dc2b9f637869unaffected
LinuxLinux4.4, 0, 6.18.40, 7.1.5, 7.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.