dbcve.org
Video Collaboration Vc1 Platform FirmwareOperating system · Qualcomm

CVE-2024-21455

HIGH · 7.8 CVSS v3.1 Published 2024-10-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Memory corruption when a compat IOCTL call is followed by another IOCTL call from userspace to a driver.

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 confidence

Memory corruption occurs in a kernel driver when a 32-bit compatibility mode (compat) IOCTL call is immediately followed by another IOCTL call from userspace. The vulnerability likely stems from improper state handling or race conditions in the driver's IOCTL dispatch mechanism when transitioning between compat and non-compat call paths, potentially allowing an attacker to corrupt kernel memory and escalate privileges.

MitigationApply vendor-provided patches for the affected driver; until patched, restrict access to the vulnerable IOCTL interface to trusted users only.

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
Video Collaboration Vc1 Platform FirmwareOperating system
Affected:all versions
Wsa8815 FirmwareOperating system
Affected:all versions
Wsa8810 FirmwareOperating system
Affected:all versions
Wcn3980 FirmwareOperating system
Affected:all versions
Wcn3950 FirmwareOperating system
Affected:all versions
Wcd9375 FirmwareOperating system
Affected:all versions
Wcd9370 FirmwareOperating system
Affected:all versions
Snapdragon Auto 5g Modem Rf Gen 2 FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify affected Qualcomm firmware components
    Examine system firmware/driver inventory for presence of any of these components: Wcd9375, Wcd9370, Wcn3950, Wcn3980, Wsa8810, Wsa8815, Vc1 Platform, or Snapdragon Auto 5g Modem Rf Gen 2. Use commands like 'ls /lib/firmware/qcom/', 'dmidecode', or vendor-specific firmware management tools to enumerate loaded firmware modules.
    Affected if Any of the listed Qualcomm firmware components are present on the system
  2. Check kernel driver IOCTL compat mode support
    Examine the kernel driver configuration and parameters for the affected component. Look for driver parameter files in /sys/module/ or /proc/ that indicate compat mode or 32-bit IOCTL support is enabled. Use 'ls -la /proc/<driver_pid>/' or check module parameters with 'modinfo <driver_name>' for compat-related flags.
    Affected if The driver exposes or supports 32-bit compatibility IOCTL interfaces and compat mode is active or configurable
  3. Verify IOCTL interface accessibility
    Check permissions on the device node or interface used to communicate with the driver IOCTL. Use 'ls -la /dev/*' or check ACLs to determine if untrusted users can invoke IOCTL calls. Examine /sys/class/ or /dev/ for device entries associated with the affected firmware components.
    Affected if The IOCTL interface is accessible to untrusted or non-privileged users who can trigger compat IOCTL calls
  4. Compare firmware version against vendor advisories
    Query the actual firmware version of the affected Qualcomm component using vendor tools (e.g., 'cat /sys/class/firmware/.../version', 'strings' on firmware binary, or Qualcomm diagnostic tools). Compare against any version information in official security advisories.
    Affected if The firmware version cannot be determined as patched, or the component is confirmed to be running unpatched firmware

A system is affected if it runs any of the listed Qualcomm firmware components and exposes a 32-bit compatibility IOCTL interface to untrusted users, with no vendor patch applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches for the affected driver; until patched, restrict access to the vulnerable IOCTL interface to trusted users only.

Fix this in Video Collaboration Vc1 Platform Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21455 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21455 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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