CVE-2024-38407

Memory corruption via raced JPEG IOCTL parameters

Published Nov 4, 2024 · Updated Nov 16, 2024

Memory corruption in the Qualcomm Snapdragon JPEG Encoder driver allows local users to corrupt memory through crafted IOCTL parameters. The driver checks IOCTL input state and later uses it after a concurrent change can invalidate the checked state. A local low-privilege process must reach the driver's IOCTL interface; Qualcomm reports no required user interaction.

CVSS severity7.8
High
EPSS probability0.07%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Memory corruption in the Qualcomm Snapdragon JPEG Encoder driver allows local users to corrupt memory through crafted IOCTL parameters. The driver checks IOCTL input state and later uses it after a concurrent change can invalidate the checked state. A local low-privilege process must reach the driver's IOCTL interface; Qualcomm reports no required user interaction.

The record

CVE
CVE-2024-38407
Published
Nov 4, 2024
Updated
Nov 16, 2024
Vendor
Qualcomm
Product
Qualcomm WCN3660B Firmware
Classifications
CWE-367, CAPEC-27, CAPEC-29
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 4, 2024CVE publishedPublication date reported by the CVE source.
  2. Nov 16, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=*

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Qualcomm · Qualcomm WCN3660B Firmwareversion=0 <=*
Qualcomm · Qualcomm WCD9375 Firmwareversion=0 <=*
Qualcomm · WSA8810 Firmwareversion=0 <=*
Qualcomm · Qualcomm Snapdragon 429 Mobile Platform Firmwareversion=0 <=*
Qualcomm · FastConnect 7800 Firmwareversion=0 <=*
Qualcomm · SC8380XP Firmwareversion=0 <=*
Qualcomm · QCM6490 Firmwareversion=0 <=*
Qualcomm · Snapdragonversion=AQT1000; version=FastConnect 6200; version=FastConnect 6700; version=FastConnect 6800; version=FastConnect 6900; version=FastConnect 7800; version=QCA6391; version=QCA6420; version=QCA6430; version=QCM5430; version=QCM6490; version=QCS5430; version=QCS6490; version=Qualcomm Video Collaboration VC3 Platform; version=SC8180X+SDX55; version=SC8380XP; version=SDM429W; version=SM6250; version=Snapdragon 429 Mobile Platform; version=Snapdragon 7c Compute Platform (SC7180-AC); version=Snapdragon 7c Gen 2 Compute Platform (SC7180-AD) "Rennell Pro"; version=Snapdragon 7c+ Gen 3 Compute; version=Snapdragon 8c Compute Platform (SC8180X-AD) "Poipu Lite"; version=Snapdragon 8c Compute Platform (SC8180XP-AD) "Poipu Lite"; version=Snapdragon 8cx Compute Platform (SC8180X-AA, AB); version=Snapdragon 8cx Compute Platform (SC8180XP-AC, AF) "Poipu Pro"; version=Snapdragon 8cx Gen 2 5G Compute Platform (SC8180X-AC, AF) "Poipu Pro"; version=Snapdragon 8cx Gen 2 5G Compute Platform (SC8180XP-AA, AB); version=Snapdragon 8cx Gen 3 Compute Platform (SC8280XP-AB, BB); version=WCD9340; version=WCD9341; version=WCD9370; version=WCD9375; version=WCD9380; version=WCD9385; version=WCN3620; version=WCN3660B; version=WSA8810; version=WSA8815; version=WSA8830; version=WSA8835; version=WSA8840; version=WSA8845; version=WSA8845H
Qualcomm · WSA8845H Firmwareversion=0 <=*
Qualcomm · Qualcomm SM6250 Firmwareversion=0 <=*
Qualcomm · QCS6490 Firmwareversion=0 <=*
Qualcomm · FastConnect 6700 Firmwareversion=0 <=*
Qualcomm · FastConnect 6900 Firmwareversion=0 <=*
Qualcomm · WCD9370 Firmwareversion=0 <=*
Qualcomm · QCA6420 Firmwareversion=0 <=*
Qualcomm · WSA8845 Firmwareversion=0 <=*
Qualcomm · Qualcomm WCD9341 Firmwareversion=0 <=*
Qualcomm · QCM5430 Firmwareversion=0 <=*
Qualcomm · QCS5430 Firmwareversion=0 <=*
Qualcomm · WCD9380 Firmwareversion=0 <=*
Qualcomm · WSA8840 Firmwareversion=0 <=*
Qualcomm · Qualcomm QCA6430 Firmwareversion=0 <=*
Qualcomm · Qualcomm WCN3620 Firmwareversion=0 <=*
Qualcomm · FastConnect 6200 Firmwareversion=0 <=*
Qualcomm · AQT1000 Firmwareversion=0 <=*
Qualcomm · WSA8830 Firmwareversion=0 <=*
Qualcomm · QCA6391 Firmwareversion=0 <=*
Qualcomm · WCD9385 Firmwareversion=0 <=*
Qualcomm · WCD9340 Firmwareversion=0 <=*
Qualcomm · WSA8835 Firmwareversion=0 <=*
Qualcomm · Qualcomm Video Collaboration VC3 Platform Firmwareversion=0 <=*
Qualcomm · FastConnect 6800 Firmwareversion=0 <=*
Qualcomm · SDM429W Firmwareversion=0 <=*
Qualcomm · WSA8815 Firmwareversion=0 <=*

Published CVSS scores

7.0NIST NVDCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
7.8Qualcomm, Inc.CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
CAPEC-27Leveraging Race Conditions via Symbolic Links
CAPEC-29Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo