{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-80670", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-08-26T14:34:25.782Z", "datePublished": "2026-08-28T06:49:11.120Z", "dateUpdated": "2026-08-29T06:21:56.727Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-29T06:21:56.727Z"}, "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->cpu[al->cpu].socket_id after checking\nal->cpu >= 0 and env->cpu != NULL, but without validating al->cpu\nagainst env->nr_cpus_avail. Since al->cpu 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->cpu before the cast to struct perf_cpu (int16_t):\nwithout this, values like 65536 silently truncate to 0, bypassing the\naccessor's internal check and returning CPU 0's topology."}], "metrics": [{"cvssV3_1": {"version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H", "baseScore": 9.1, "baseSeverity": "CRITICAL"}, "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 >= 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->cpu[al->cpu].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->socket; 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."}]}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["tools/perf/util/event.c"], "versions": [{"version": "0c4c4debb0adda4c18c158d95031dc2b9f637869", "lessThan": "b9e8406651dcc1c19238aad11861a758683525b4", "status": "affected", "versionType": "git"}, {"version": "0c4c4debb0adda4c18c158d95031dc2b9f637869", "lessThan": "eb266a14c16a93eb4db7b56a452d6be93f8bdcd4", "status": "affected", "versionType": "git"}, {"version": "0c4c4debb0adda4c18c158d95031dc2b9f637869", "lessThan": "5484b43a0ec8231c36fba6ead654cb72dbba8b8f", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["tools/perf/util/event.c"], "versions": [{"version": "4.4", "status": "affected"}, {"version": "0", "lessThan": "4.4", "status": "unaffected", "versionType": "semver"}, {"version": "6.18.40", "lessThanOrEqual": "6.18.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.1.5", "lessThanOrEqual": "7.1.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.2", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "4.4", "versionEndExcluding": "6.18.40"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "4.4", "versionEndExcluding": "7.1.5"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "4.4", "versionEndExcluding": "7.2"}]}]}], "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"}}}}

{}

{"affected": [{"affectedData": [{"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"}]}], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "cveTags": [], "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->cpu[al->cpu].socket_id after checking\nal->cpu >= 0 and env->cpu != NULL, but without validating al->cpu\nagainst env->nr_cpus_avail. Since al->cpu 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->cpu before the cast to struct perf_cpu (int16_t):\nwithout this, values like 65536 silently truncate to 0, bypassing the\naccessor's internal check and returning CPU 0's topology."}], "id": "CVE-2026-80670", "lastModified": "2026-08-29T07:16:49.340", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 9.1, "baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 5.2, "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "type": "Secondary"}]}, "published": "2026-08-28T08:16:52.317", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/5484b43a0ec8231c36fba6ead654cb72dbba8b8f"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/b9e8406651dcc1c19238aad11861a758683525b4"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/eb266a14c16a93eb4db7b56a452d6be93f8bdcd4"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Received"}

{"bugzilla": {"description": "kernel: perf tools: Use perf_env__get_cpu_topology() in machine__resolve()", "id": "2525391", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2525391"}, "csaw": false, "cvss3": {"cvss3_base_score": "5.5", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "status": "draft"}, "cwe": "CWE-1285", "details": ["In the Linux kernel, the following vulnerability has been resolved:\nperf tools: Use perf_env__get_cpu_topology() in machine__resolve()\nmachine__resolve() accesses env->cpu[al->cpu].socket_id after checking\nal->cpu >= 0 and env->cpu != NULL, but without validating al->cpu\nagainst env->nr_cpus_avail. Since al->cpu comes from the untrusted\nperf.data sample, a crafted file with a large CPU index causes an\nout-of-bounds heap read.\nUse perf_env__get_cpu_topology() which validates both NULL and bounds.\nAlso bounds-check al->cpu before the cast to struct perf_cpu (int16_t):\nwithout this, values like 65536 silently truncate to 0, bypassing the\naccessor's internal check and returning CPU 0's topology.", "A flaw was found in the Linux kernel's perf tools. The `machine__resolve()` function, responsible for resolving machine addresses, does not properly validate CPU index values from untrusted `perf.data` samples. A local attacker could provide a specially crafted `perf.data` file with a large CPU index, leading to an out-of-bounds heap read. This could result in information disclosure or a denial of service."], "name": "CVE-2026-80670", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:10", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 10"}, {"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 9"}], "public_date": "2026-08-28T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-80670\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-80670\nhttps://lore.kernel.org/linux-cve-announce/2026082848-CVE-2026-80670-bbb7@gregkh/T"], "threat_severity": "Moderate"}