CVE-2026-80670 (GCVE-0-2026-80670)
Vulnerability from cvelistv5
Published
2026-08-28 06:49
Modified
2026-08-29 06:21
Severity ?
VLAI Severity ?
EPSS score ?
Summary
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.
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"tools/perf/util/event.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "b9e8406651dcc1c19238aad11861a758683525b4",
"status": "affected",
"version": "0c4c4debb0adda4c18c158d95031dc2b9f637869",
"versionType": "git"
},
{
"lessThan": "eb266a14c16a93eb4db7b56a452d6be93f8bdcd4",
"status": "affected",
"version": "0c4c4debb0adda4c18c158d95031dc2b9f637869",
"versionType": "git"
},
{
"lessThan": "5484b43a0ec8231c36fba6ead654cb72dbba8b8f",
"status": "affected",
"version": "0c4c4debb0adda4c18c158d95031dc2b9f637869",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"tools/perf/util/event.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.4"
},
{
"lessThan": "4.4",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.40",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.40",
"versionStartIncluding": "4.4",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1.5",
"versionStartIncluding": "4.4",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "4.4",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nperf tools: Use perf_env__get_cpu_topology() in machine__resolve()\n\nmachine__resolve() accesses env-\u003ecpu[al-\u003ecpu].socket_id after checking\nal-\u003ecpu \u003e= 0 and env-\u003ecpu != NULL, but without validating al-\u003ecpu\nagainst env-\u003enr_cpus_avail. Since al-\u003ecpu comes from the untrusted\nperf.data sample, a crafted file with a large CPU index causes an\nout-of-bounds heap read.\n\nUse perf_env__get_cpu_topology() which validates both NULL and bounds.\nAlso bounds-check al-\u003ecpu before the cast to struct perf_cpu (int16_t):\nwithout this, values like 65536 silently truncate to 0, bypassing the\naccessor\u0027s internal check and returning CPU 0\u0027s topology."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 9.1,
"baseSeverity": "CRITICAL",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:N - machine__resolve() is reached when perf tools parse untrusted perf.data samples via perf report/script/mem/kvm/diff and related builtins; recordings are routinely ingested over the network through stdin pipes (perf -i -) or automated CI/profiling services that analyze uploaded artifacts, giving a remote attacker a network path to supply the malicious CPU index.\nAC:L - The attacker fully controls sample.cpu in the crafted perf.data PERF_RECORD_SAMPLE payload; once perf opens the file or pipe, a single sample with cpu \u003e= nr_cpus_avail deterministically triggers the out-of-bounds read without races, timing, or uncontrollable memory layout.\nPR:N - Processing malicious perf.data requires no Linux capabilities or init-namespace root; any remote party who can supply a recording to a profiling pipeline, bug-report workflow, or piped perf session can trigger the bug on the analyzing host without local account privileges on that system.\nUI:N - No interactive victim action beyond normal automated ingestion of perf recordings is required; an attacker can deliver a crafted file to CI bots, shared profiling servers, or piped analysis sessions that invoke perf non-interactively, without the analyst manually opening attachments.\nS:U - The flaw is confined to the userspace perf tool process parsing the recording; impact does not cross VM, IOMMU, or container/kernel security boundaries and remains within the same security authority as the perf analyzer process.\nC:H - The bug is an attacker-controlled out-of-bounds heap read through env-\u003ecpu[al-\u003ecpu].socket_id with no upper bound on the index relative to the allocated topology array, enabling disclosure of adjacent heap contents (metadata, pointers, strings) from the perf process address space.\nI:N - The vulnerability performs only an out-of-bounds read of topology fields into al-\u003esocket; it does not write memory, corrupt heap metadata, or provide a direct arbitrary-write or code-execution primitive in the vulnerable code path.\nA:H - An out-of-bounds heap read with a large crafted CPU index commonly causes an immediate SIGSEGV or abort of the perf analysis process, denying availability of profiling, CI performance triage, and incident-response workflows that depend on perf report/script completing successfully."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-29T06:21:56.727Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/b9e8406651dcc1c19238aad11861a758683525b4"
},
{
"url": "https://git.kernel.org/stable/c/eb266a14c16a93eb4db7b56a452d6be93f8bdcd4"
},
{
"url": "https://git.kernel.org/stable/c/5484b43a0ec8231c36fba6ead654cb72dbba8b8f"
}
],
"title": "perf tools: Use perf_env__get_cpu_topology() in machine__resolve()",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-80670",
"datePublished": "2026-08-28T06:49:11.120Z",
"dateReserved": "2026-08-26T14:34:25.782Z",
"dateUpdated": "2026-08-29T06:21:56.727Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…