PT-2026-64598 · Linux · Linux

CVE-2026-64377

·

Publicado

2026-07-25

·

Atualizado

2026-07-25

Nenhuma

Não há classificações de severidade ou métricas disponíveis. Quando houver, atualizaremos as informações correspondentes na página.
In the Linux kernel, the following vulnerability has been resolved:
cpufreq: qcom-cpufreq-hw: Fix possible double free
qcom cpufreq.data is allocated with devm kzalloc() in probe() as an array of per-domain data. qcom cpufreq hw cpu init() stores a pointer to one element of this array in policy->driver data.
qcom cpufreq hw cpu exit() currently calls kfree() on policy->driver data. This is not valid because the memory is devm-managed. For the first domain, this can free the devm-managed allocation while the devres entry is still active, leading to a possible double free when the platform device is later detached. For other domains, the pointer may refer to an element inside the array rather than the allocation base.
Remove the kfree(data) call and let devres release qcom cpufreq.data.
This issue was found by a static analysis tool I am developing.
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾

Identificadores relacionados

CVE-2026-64377

Produtos afetados

Linux