CVE-2024-45561
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 · uneditedMemory corruption while handling IOCTL call from user-space to set latency level.
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 confidenceMemory corruption vulnerability in kernel driver when handling IOCTL call from user-space to set latency level. This allows a local attacker to potentially escalate privileges or cause denial of service via malformed IOCTL requests.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Qualcomm wireless hardware on the systemRun 'lspci | grep -i network' or 'lspci | grep -i qualcomm' for PCIe wireless cards. For USB, run 'lsusb' and look for Qualcomm device IDs. Check 'ip link show' for wireless interfaces and their drivers.Affected if The system contains any Qualcomm Aqt1000, Fastconnect 6200/6700/6800/6900/7800, Qca6391, or Qca6420 wireless adapter.
-
Locate the kernel driver for the Qualcomm deviceRun 'lsmod' and check for drivers such as 'ath11k', 'qca6390', 'qcn9024' or similar Qualcomm wireless kernel modules. Also check 'dmesg | grep -i qualcomm' for driver loading messages.Affected if A Qualcomm wireless kernel driver is loaded (the vulnerable IOCTL handler resides in this driver).
-
Verify the IOCTL interface existsCheck if the device node for the driver exists: look in /dev/ for device files related to the wireless driver, or check /sys/class/net/* for wireless interfaces and examine associated driver sysfs entries. Use 'ls -la /dev/ath*' or similar based on interface name found.Affected if The character device or net device node created by the Qualcomm driver is present, indicating the IOCTL interface is exposed.
-
Check for signs of exploitation attemptsReview system logs: 'dmesg', 'journalctl -k', and /var/log/messages for any crash logs, kernel oops, or memory corruption indicators related to the wireless driver. Look for patterns like 'BUG:', 'WARNING:', or 'unable to handle page fault'.Affected if Kernel crashes, oops messages, or memory corruption logs involving the Qualcomm wireless driver are present.
The system is affected if it has any Qualcomm wireless hardware (Aqt1000, Fastconnect 6200/6700/6800/6900/7800, Qca6391, Qca6420) with the vulnerable kernel driver loaded and the IOCTL interface exposed, since all firmware versions are vulnerable.
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.
From vendor dataApply vendor patch for the affected kernel driver; implement proper bounds checking and validate all IOCTL input parameters before memory operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45561 — 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-2024-45561 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