CVE-2024-45560
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 taking a snapshot with hardware encoder due to unvalidated userspace buffer.
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 memory corruption vulnerability exists in the hardware encoder's snapshot functionality where an unvalidated userspace buffer is used without proper bounds checking or validation, allowing an attacker to trigger memory corruption by providing a crafted buffer during snapshot operations.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 firmware componentsCheck system information or firmware manifests for presence of Qualcomm Aqt1000, Fastconnect 6200/6700/6800/6900/7800, Qca6391, or Qca6420 firmware. On Linux, this may appear in 'lspci', 'dmesg', '/lib/firmware/', or device manager outputs.Affected if Any of the listed Qualcomm firmware components are present on the system
-
Verify hardware encoder module is loadedCheck if the hardware encoder kernel module or firmware interface is active. Look for encoder-related kernel modules, device nodes (/dev/video*, /dev/encoder*), or firmware driver loaded messages in system logs (dmesg, journalctl).Affected if The hardware encoder module or driver is loaded and operational on the system
-
Confirm snapshot functionality is in useInspect system logs, application usage, or configuration for evidence of snapshot operations using the hardware encoder. This may include snapshot API calls, encoder snapshot buffers, or related feature usage in media applications.Affected if The snapshot feature of the hardware encoder has been invoked or configured for use
-
Check firmware versionQuery the installed firmware version via vendor tools, system diagnostic utilities, or firmware revision strings (e.g., 'cat /sys/class/firmware/.../version', vendor-specific tools like 'ath11k-firmware-query' or similar).Affected if The firmware version matches any of the affected product names listed (all versions are vulnerable)
The system is potentially affected if it contains any of the listed Qualcomm firmware components and the hardware encoder snapshot feature is being used, since all versions of these products 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 dataImplement rigorous validation of all userspace buffers before use in hardware encoder operations, including bounds checking and ensuring proper memory access patterns. Consider adding input sanitization and using safe memory copy functions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45560 — 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-45560 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