{"api_version":"1","generated_at":"2026-08-28T14:43:07+00:00","cve":"CVE-2026-80670","urls":{"html":"https://cve.report/CVE-2026-80670","api":"https://cve.report/api/cve/CVE-2026-80670.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80670","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80670"},"summary":{"title":"perf tools: Use perf_env__get_cpu_topology() in machine__resolve()","description":"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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-28 08:16:52","updated_at":"2026-08-28 08:16:52"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/eb266a14c16a93eb4db7b56a452d6be93f8bdcd4","name":"https://git.kernel.org/stable/c/eb266a14c16a93eb4db7b56a452d6be93f8bdcd4","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5484b43a0ec8231c36fba6ead654cb72dbba8b8f","name":"https://git.kernel.org/stable/c/5484b43a0ec8231c36fba6ead654cb72dbba8b8f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b9e8406651dcc1c19238aad11861a758683525b4","name":"https://git.kernel.org/stable/c/b9e8406651dcc1c19238aad11861a758683525b4","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80670","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80670","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0c4c4debb0adda4c18c158d95031dc2b9f637869 b9e8406651dcc1c19238aad11861a758683525b4 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0c4c4debb0adda4c18c158d95031dc2b9f637869 eb266a14c16a93eb4db7b56a452d6be93f8bdcd4 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 0c4c4debb0adda4c18c158d95031dc2b9f637869 5484b43a0ec8231c36fba6ead654cb72dbba8b8f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.4","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.4 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.40 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"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->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."}],"providerMetadata":{"dateUpdated":"2026-08-28T06:49:11.120Z","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-28T06:49:11.120Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-28 08:16:52","lastModifiedDate":"2026-08-28 08:16:52","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80670","Ordinal":"1","Title":"perf tools: Use perf_env__get_cpu_topology() in machine__resolve","CVE":"CVE-2026-80670","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80670","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"perf tools: Use perf_env__get_cpu_topology() in machine__resolve"}]}}}