Service interruption via double resource release
Published Jun 19, 2023 · Updated Apr 23, 2025
Double free in the Linux Kernel before 6.4-rc1 allows attackers to interrupt service by unbinding a Qualcomm CPU-frequency device. qcom_cpufreq_hw_cpu_exit releases an I/O mapping and memory resource that device-managed cleanup releases again during unbind. Reachability requires the Qualcomm qcom-cpufreq-hw driver and the ability to initiate device unbinding; the published record does not define the attacker's access level.
Summary
What happened
Double free in the Linux Kernel before 6.4-rc1 allows attackers to interrupt service by unbinding a Qualcomm CPU-frequency device. qcom_cpufreq_hw_cpu_exit releases an I/O mapping and memory resource that device-managed cleanup releases again during unbind. Reachability requires the Qualcomm qcom-cpufreq-hw driver and the ability to initiate device unbinding; the published record does not define the attacker's access level.
The record
- CVE
- CVE-2023-3312
- Published
- Jun 19, 2023
- Updated
- Apr 23, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-415
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 19, 2023CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Kernel version prior to 6.4-rc1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo