CVE-2024-38399: Use After Free in Graphics
Noroxi assessment
Priority: Monitor (action score 31/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (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 processing user packets to generate page faults.
- Published
- Oct 7, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 6th 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
- 7.8
- CNA · qualcomm
- 8.4
- 0.6 point gap
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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
- Proof of concept exists, no weaponized module
- 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 | qca6574au | cpe:2.3:h:qualcomm:qca6574au |
| qualcomm | wsa8835 firmware | cpe:2.3:o:qualcomm:wsa8835_firmware |
| qualcomm | wsa8835 | cpe:2.3:h:qualcomm:wsa8835 |
| qualcomm | wsa8830 firmware | cpe:2.3:o:qualcomm:wsa8830_firmware |
| qualcomm | wsa8830 | cpe:2.3:h:qualcomm:wsa8830 |
| qualcomm | wsa8810 firmware | cpe:2.3:o:qualcomm:wsa8810_firmware |
| qualcomm | wsa8810 | cpe:2.3:h:qualcomm:wsa8810 |
| qualcomm | wcn3950 firmware | cpe:2.3:o:qualcomm:wcn3950_firmware |
| qualcomm | wcn3950 | cpe:2.3:h:qualcomm:wcn3950 |
| qualcomm | wcd9380 firmware | cpe:2.3:o:qualcomm:wcd9380_firmware |
| qualcomm | wcd9380 | cpe:2.3:h:qualcomm:wcd9380 |
| qualcomm | wcd9375 firmware | cpe:2.3:o:qualcomm:wcd9375_firmware |
and 68 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
- FastConnect 6900, FastConnect 7800, QAM8255P, QAM8295P, QAM8650P, QAM8775P, QAMSRV1H, QAMSRV1M, QCA6574AU, QCA6595, QCA6595AU, QCA6688AQ … (+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 fastconnect 6900 firmwareall versions
- qualcomm fastconnect 7800 firmwareall versions
- qualcomm qam8255p firmwareall versions
- qualcomm qam8295p firmwareall versions
- qualcomm qam8650p firmwareall versions
- qualcomm qam8775p firmwareall versions
- qualcomm qamsrv1h firmwareall versions
- qualcomm qamsrv1m firmwareall versions
- qualcomm qca6574au firmwareall versions
- qualcomm qca6595 firmwareall versions
- qualcomm qca6595au firmwareall versions
- qualcomm qca6688aq firmwareall versions
- qualcomm qca6696 firmwareall versions
- qualcomm qca6698aq firmwareall versions
- qualcomm qca6797aq firmwareall versions
- qualcomm sa6155p firmwareall versions
- qualcomm sa7255p firmwareall versions
- qualcomm sa7775p firmwareall versions
- qualcomm sa8155p firmwareall versions
- qualcomm sa8195p firmwareall versions
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-25268Stack-based Buffer Overflow in WLAN Host35Monitor
- CVE-2024-38423Buffer Copy Without Checking Size of Input in Graphics Linux31Monitor
- CVE-2024-33069Use After Free in WLAN Host30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-23376Oct 7, 2024 · Use After Free in ComputerVision26Monitor
- ← EarlierCVE-2024-23379Oct 7, 2024 · Double Free in DSP Services26Monitor
- Later →CVE-2024-38425Oct 7, 2024 · Improper Authorization in Performance24Monitor
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
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:25 | 2025-02-02 |
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.
- Published
- First PoC+118 d
- TodayNov 16, 2026+770 d
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-330690 days apartUse After Free in WLAN Host30Monitor
- CVE-2024-233700 days apartUse After Free in Automotive Multimedia26Monitor
- CVE-2024-233760 days apartUse After Free in ComputerVision26Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1630 · Oct 8, 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-primary
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.