CVE-2024-38419: Use After Free in Automotive GPU
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.10% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Memory corruption while invoking IOCTL calls from the use-space for HGSL memory node.
- Published
- Nov 4, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 0th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · qualcomm
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| qualcomm | wsa8845h firmware | cpe:2.3:o:qualcomm:wsa8845h_firmware |
| qualcomm | wsa8845h | cpe:2.3:h:qualcomm:wsa8845h |
| qualcomm | wsa8845 firmware | cpe:2.3:o:qualcomm:wsa8845_firmware |
| qualcomm | wsa8845 | cpe:2.3:h:qualcomm:wsa8845 |
| qualcomm | wsa8840 firmware | cpe:2.3:o:qualcomm:wsa8840_firmware |
| qualcomm | wsa8840 | cpe:2.3:h:qualcomm:wsa8840 |
| qualcomm | wsa8835 firmware | cpe:2.3:o:qualcomm:wsa8835_firmware |
| qualcomm | wsa8835 | cpe:2.3:h:qualcomm:wsa8835 |
| qualcomm | wsa8832 firmware | cpe:2.3:o:qualcomm:wsa8832_firmware |
| qualcomm | wsa8832 | cpe:2.3:h:qualcomm:wsa8832 |
| qualcomm | wsa8830 firmware | cpe:2.3:o:qualcomm:wsa8830_firmware |
| qualcomm | wsa8830 | cpe:2.3:h:qualcomm:wsa8830 |
and 188 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (qualcomm). Independent of NVD's CPE analysis and usually ahead of it.
Qualcomm, Inc. Snapdragon
- AR8035, CSRA6620, CSRA6640, FastConnect 6200, FastConnect 6700, FastConnect 6900, FastConnect 7800, Flight RB5 5G Platform, MDM9628, QAM8255P, QAM8295P, QAM8620P … (+28)affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm ar8035 firmwareall versions
- qualcomm csra6620 firmwareall versions
- qualcomm csra6640 firmwareall versions
- qualcomm fastconnect 6200 firmwareall versions
- qualcomm fastconnect 6700 firmwareall versions
- qualcomm fastconnect 6900 firmwareall versions
- qualcomm fastconnect 7800 firmwareall versions
- qualcomm flight rb5 5g platform firmwareall versions
- qualcomm mdm9628 firmwareall versions
- qualcomm qam8255p firmwareall versions
- qualcomm qam8295p firmwareall versions
- qualcomm qam8620p firmwareall versions
- qualcomm qam8650p firmwareall versions
- qualcomm qam8775p firmwareall versions
- qualcomm qamsrv1h firmwareall versions
- qualcomm qamsrv1m firmwareall versions
- qualcomm qca6174a firmwareall versions
- qualcomm qca6391 firmwareall versions
- qualcomm qca6564a firmwareall versions
- qualcomm qca6564au firmwareall versions
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-38408Cryptographic Issues in BT Controller36Monitor
- CVE-2024-23384Use After Free in Graphics Linux33Monitor
- CVE-2024-33073Buffer Over-read in WLAN Host Communication32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-38410Nov 4, 2024 · Stack-based Buffer Overflow in WLAN Windows Host31Monitor
- ← EarlierCVE-2024-38415Nov 4, 2024 · Use After Free in Computer Vision31Monitor
- Later →CVE-2024-38421Nov 4, 2024 · Use After Free in Graphics Linux31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-2338491 days apartUse After Free in Graphics Linux33Monitor
- CVE-2024-330330 days apartUse After Free in ComputerVision31Monitor
- CVE-2024-384150 days apartUse After Free in Computer Vision31Monitor
- CVE-2024-384210 days apartUse After Free in Graphics Linux31Monitor
- CVE-2024-2338191 days apartUse After Free in Graphics Linux31Monitor
- CVE-2024-2338391 days apartUse After Free in Graphics Linux31Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1821 · Nov 5, 2024(Qualcomm Çoklu Ürün Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.