Linux KernelOperating system · Linux
CVE-2023-3312
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was found in drivers/cpufreq/qcom-cpufreq-hw.c in cpufreq subsystem in the Linux Kernel. This flaw, during device unbind will lead to double release problem leading to denial of service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA double-release vulnerability exists in the Qualcomm cpufreq hardware driver (qcom-cpufreq-hw.c) in the Linux Kernel's cpufreq subsystem. When a device is unbound from the driver, the same resource is freed twice due to improper cleanup handling, leading to a use-after-free condition and resulting in denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Linux KernelOperating system
>= 6.2, < 6.2.15>= 6.3, < 6.3.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the running kernel versionRun 'uname -r' or check /proc/version to get the exact kernel version stringAffected if The version falls within >= 6.2 and < 6.2.15, or >= 6.3 and < 6.3.2
-
Verify qcom-cpufreq-hw driver presenceCheck if the driver is available by examining /sys/module/ for 'qcom_cpufreq_hw' or by searching kernel config for CONFIG_QCOM_CPUFREQ_HW=y or =mAffected if The driver is compiled into the kernel or loaded as a module on an affected kernel version
-
Confirm Qualcomm cpufreq hardware exists in the systemLook for cpufreq policy directories in /sys/devices/system/cpu/cpufreq/ that reference qcom hardware, or check dmesg for 'qcom-cpufreq-hw' initialization messagesAffected if Qualcomm cpufreq hardware devices managed by qcom-cpufreq-hw are present and actively being used
You are affected if your kernel version is in the vulnerable range AND the qcom-cpufreq-hw driver is present managing Qualcomm cpufreq hardware, particularly when device unbinding operations are performed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.2.156.3.2
Apply the upstream Linux Kernel patch addressing the double-release in qcom-cpufreq-hw.c, or update to a kernel version containing the fix. Until patched, avoid unbinding cpufreq devices on affected Qualcomm hardware.
Linux Kernel 6.2.15 or later, or 6.3.2 or later (whichever branch is applicable)
- Identify the currently running Linux kernel version using `uname -r`
- For systems running kernel 6.2.x (6.2.0 through 6.2.14): Upgrade to kernel version 6.2.15 or later from your distribution's kernel repository
- For systems running kernel 6.3.x (6.3.0 through 6.3.1): Upgrade to kernel version 6.3.2 or later from your distribution's kernel repository
- After kernel upgrade, reboot the system to load the fixed kernel
- Verify the new kernel version is running with `uname -r`
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3312 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-3312 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data