dbcve.org
Fastconnect 6200 FirmwareOperating system · Qualcomm

CVE-2024-23382

HIGH · 7.8 CVSS v3.1 Published 2024-08-05
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 while processing graphics kernel driver request to create DMA fence.

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

A memory corruption vulnerability exists in a graphics kernel driver's DMA fence creation path. When processing a request to create a DMA fence, the driver fails to properly handle memory allocation or validation, leading to memory corruption that could allow local privilege escalation or denial of service.

MitigationApply vendor-supplied patches for the affected graphics kernel driver. Until a patch is available, consider disabling the affected graphics driver or restricting access to graphics-intensive 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 data
Fastconnect 6200 FirmwareOperating system
Affected:all versions
Fastconnect 6700 FirmwareOperating system
Affected:all versions
Fastconnect 6900 FirmwareOperating system
Affected:all versions
Fastconnect 7800 FirmwareOperating system
Affected:all versions
Flight Rb5 5g Platform FirmwareOperating system
Affected:all versions
Qam8255p FirmwareOperating system
Affected:all versions
Qam8295p FirmwareOperating system
Affected:all versions
Qam8620p 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 Qualcomm graphics/network components
    Run 'lspci' or check system device listings for Qualcomm Fastconnect adapters, or check '/proc/bus/pci' for Qualcomm network/graphics devices. On mobile/embedded systems, check '/sys/class/net' or use 'nmcli device' to list network interfaces.
    Affected if Any Qualcomm Fastconnect (6200/6700/6900/7800), Flight Rb5 5g, QAM8255p, QAM8295p, or QAM8620p devices are present in the system
  2. Check for loaded graphics kernel drivers
    Run 'lsmod' to list loaded kernel modules and look for graphics-related drivers, or check '/proc/modules'. On Android, use 'ls /vendor/lib/modules/' or check 'dmesg' for graphics driver loading messages.
    Affected if Any graphics kernel drivers from Qualcomm are loaded and active
  3. Verify DMA fence functionality exposure
    Check if graphics acceleration or DMA buffer APIs are accessible by examining '/dev/dri/' directory contents (on systems with Direct Rendering Infrastructure), or check for ioctl calls related to DMA fences in graphics driver debug logs.
    Affected if DMA fence creation path is exposed through accessible graphics APIs or device nodes
  4. Check firmware version of Qualcomm components
    Use vendor-specific tools or check '/sys/firmware/efi/fwmap' or '/lib/firmware/qcom' directories for loaded firmware files. For Fastconnect, check via 'iw list' or 'lshw' network adapter details.
    Affected if Any Qualcomm Fastconnect, Flight Rb5, or QAM firmware is loaded (all versions are affected)
  5. Review system logs for graphics driver errors
    Check 'dmesg', 'journalctl -b', or '/var/log/syslog' for messages containing 'dma_fence', 'graphics', or 'memory corruption' related to Qualcomm graphics drivers.
    Affected if Error messages indicate DMA fence issues in Qualcomm graphics components

If the system has any Qualcomm Fastconnect, Flight Rb5 5g, or QAM (8255p/8295p/8620p) firmware with an active graphics driver exposing DMA fence functionality, the environment is affected since all versions of these products are vulnerable.

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-supplied patches for the affected graphics kernel driver. Until a patch is available, consider disabling the affected graphics driver or restricting access to graphics-intensive operations.

Fix this in Fastconnect 6200 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-23382 — 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-23382 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