CVE-2026-64377

Last refreshed2026-10-23

Status: UPDATED | Advisory ID: CVE-2026-64377

Key Details

CVE	CVE-2026-64377
CVSS Score / Version	7.8 (High) / CVSS v3.1
Updated	2026-10-21
CVSS Vector	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`
CVSS Prose	attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products	Linux Kernel
Classified as	CWE-415 (Double Free)

Vendor	Product	Affected Versions	Patch Status
Linux	Linux Kernel

Vendor

Product

Affected Versions

Patch Status

Linux

Linux Kernel

Subsystems	OT Supporting Infrastructure
Sectors	All Sectors

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. (NVD)

Monitor Linux's web page for any future patch releases.

Source	Reference
NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-64377
CVE	https://www.cve.org/CVERecord?id=CVE-2026-64377

Source

Reference

NVD

CVE