Linux
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0c4c4debb0adda4c18c158d95031dc2b9f637869, < b9e8406651dcc1c19238aad11861a758683525b4
- >= 0c4c4debb0adda4c18c158d95031dc2b9f637869, < eb266a14c16a93eb4db7b56a452d6be93f8bdcd4
- >= 0c4c4debb0adda4c18c158d95031dc2b9f637869, < 5484b43a0ec8231c36fba6ead654cb72dbba8b8f
Fixed in b9e8406651dcc1c19238aad11861a758683525b4, eb266a14c16a93eb4db7b56a452d6be93f8bdcd4, 5484b43a0ec8231c36fba6ead654cb72dbba8b8f
- 4.4
Fixed in 0, 6.18.40, 7.1.5, 7.2
Mitigation
Upgrade Linux to b9e8406651dcc1c19238aad11861a758683525b4 or eb266a14c16a93eb4db7b56a452d6be93f8bdcd4 or 5484b43a0ec8231c36fba6ead654cb72dbba8b8f or later.
Upgrade Linux to 0 or 6.18.40 or 7.1.5 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.