{"api_version":"1","generated_at":"2026-08-01T23:25:10+00:00","cve":"CVE-2026-64377","urls":{"html":"https://cve.report/CVE-2026-64377","api":"https://cve.report/api/cve/CVE-2026-64377.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-64377","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-64377"},"summary":{"title":"cpufreq: qcom-cpufreq-hw: Fix possible double free","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: qcom-cpufreq-hw: Fix possible double free\n\nqcom_cpufreq.data is allocated with devm_kzalloc() in probe() as an\narray of per-domain data. qcom_cpufreq_hw_cpu_init() stores a pointer to\none element of this array in policy->driver_data.\n\nqcom_cpufreq_hw_cpu_exit() currently calls kfree() on policy->driver_data.\nThis is not valid because the memory is devm-managed. For the first\ndomain, this can free the devm-managed allocation while the devres entry\nis still active, leading to a possible double free when the platform\ndevice is later detached. For other domains, the pointer may refer to an\nelement inside the array rather than the allocation base.\n\nRemove the kfree(data) call and let devres release qcom_cpufreq.data.\n\nThis issue was found by a static analysis tool I am developing.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-25 10:17:20","updated_at":"2026-07-25 10:17:20"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/bcb8889c4981fdde42d4fd2c29a77d510fe21da2","name":"https://git.kernel.org/stable/c/bcb8889c4981fdde42d4fd2c29a77d510fe21da2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e904961332801c87355f5d11c65bb433e717c489","name":"https://git.kernel.org/stable/c/e904961332801c87355f5d11c65bb433e717c489","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/28a03a3f6e6cda0b0da3b43761d175dec5d14d13","name":"https://git.kernel.org/stable/c/28a03a3f6e6cda0b0da3b43761d175dec5d14d13","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d","name":"https://git.kernel.org/stable/c/9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-64377","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64377","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 054a3ef683a176a509cc9b37f762029aae942495 28a03a3f6e6cda0b0da3b43761d175dec5d14d13 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 054a3ef683a176a509cc9b37f762029aae942495 e904961332801c87355f5d11c65bb433e717c489 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 054a3ef683a176a509cc9b37f762029aae942495 9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 054a3ef683a176a509cc9b37f762029aae942495 bcb8889c4981fdde42d4fd2c29a77d510fe21da2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.2","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.2 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.96 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.39 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.4 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"64377","cve":"CVE-2026-64377","epss":"0.001680000","percentile":"0.064530000","score_date":"2026-07-28","updated_at":"2026-07-29 00:05:33"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/cpufreq/qcom-cpufreq-hw.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"28a03a3f6e6cda0b0da3b43761d175dec5d14d13","status":"affected","version":"054a3ef683a176a509cc9b37f762029aae942495","versionType":"git"},{"lessThan":"e904961332801c87355f5d11c65bb433e717c489","status":"affected","version":"054a3ef683a176a509cc9b37f762029aae942495","versionType":"git"},{"lessThan":"9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d","status":"affected","version":"054a3ef683a176a509cc9b37f762029aae942495","versionType":"git"},{"lessThan":"bcb8889c4981fdde42d4fd2c29a77d510fe21da2","status":"affected","version":"054a3ef683a176a509cc9b37f762029aae942495","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/cpufreq/qcom-cpufreq-hw.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.2"},{"lessThan":"6.2","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.96","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.39","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.96","versionStartIncluding":"6.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.39","versionStartIncluding":"6.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.4","versionStartIncluding":"6.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc1","versionStartIncluding":"6.2","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: qcom-cpufreq-hw: Fix possible double free\n\nqcom_cpufreq.data is allocated with devm_kzalloc() in probe() as an\narray of per-domain data. qcom_cpufreq_hw_cpu_init() stores a pointer to\none element of this array in policy->driver_data.\n\nqcom_cpufreq_hw_cpu_exit() currently calls kfree() on policy->driver_data.\nThis is not valid because the memory is devm-managed. For the first\ndomain, this can free the devm-managed allocation while the devres entry\nis still active, leading to a possible double free when the platform\ndevice is later detached. For other domains, the pointer may refer to an\nelement inside the array rather than the allocation base.\n\nRemove the kfree(data) call and let devres release qcom_cpufreq.data.\n\nThis issue was found by a static analysis tool I am developing."}],"providerMetadata":{"dateUpdated":"2026-07-25T08:50:28.299Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/28a03a3f6e6cda0b0da3b43761d175dec5d14d13"},{"url":"https://git.kernel.org/stable/c/e904961332801c87355f5d11c65bb433e717c489"},{"url":"https://git.kernel.org/stable/c/9de568ef6cdfc7912d5ea8db02843c0e4ef0c75d"},{"url":"https://git.kernel.org/stable/c/bcb8889c4981fdde42d4fd2c29a77d510fe21da2"}],"title":"cpufreq: qcom-cpufreq-hw: Fix possible double free","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-64377","datePublished":"2026-07-25T08:50:28.299Z","dateReserved":"2026-07-19T15:36:31.784Z","dateUpdated":"2026-07-25T08:50:28.299Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-25 10:17:20","lastModifiedDate":"2026-07-25 10:17:20","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"64377","Ordinal":"1","Title":"cpufreq: qcom-cpufreq-hw: Fix possible double free","CVE":"CVE-2026-64377","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"64377","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: qcom-cpufreq-hw: Fix possible double free\n\nqcom_cpufreq.data is allocated with devm_kzalloc() in probe() as an\narray of per-domain data. qcom_cpufreq_hw_cpu_init() stores a pointer to\none element of this array in policy->driver_data.\n\nqcom_cpufreq_hw_cpu_exit() currently calls kfree() on policy->driver_data.\nThis is not valid because the memory is devm-managed. For the first\ndomain, this can free the devm-managed allocation while the devres entry\nis still active, leading to a possible double free when the platform\ndevice is later detached. For other domains, the pointer may refer to an\nelement inside the array rather than the allocation base.\n\nRemove the kfree(data) call and let devres release qcom_cpufreq.data.\n\nThis issue was found by a static analysis tool I am developing.","Type":"Description","Title":"cpufreq: qcom-cpufreq-hw: Fix possible double free"}]}}}