Improper Release of Memory Before Removing Last Reference in Graphics
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.
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 when initiating GPU memory mapping using scatter-gather lists due to unchecked IOMMU mapping errors.
- Published
- Feb 2, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-401
Report tools
Action score
31
Monitor
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 | fastconnect 6900 firmware | cpe:2.3:o:qualcomm:fastconnect_6900_firmware |
| qualcomm | fastconnect 6900 | cpe:2.3:h:qualcomm:fastconnect_6900 |
| qualcomm | fastconnect 7800 firmware | cpe:2.3:o:qualcomm:fastconnect_7800_firmware |
| qualcomm | fastconnect 7800 | cpe:2.3:h:qualcomm:fastconnect_7800 |
| qualcomm | flight rb5 5g firmware | cpe:2.3:o:qualcomm:flight_rb5_5g_firmware |
| qualcomm | flight rb5 5g | cpe:2.3:h:qualcomm:flight_rb5_5g |
| qualcomm | g1 gen 1 firmware | cpe:2.3:o:qualcomm:g1_gen_1_firmware |
| qualcomm | g1 gen 1 | cpe:2.3:h:qualcomm:g1_gen_1 |
| qualcomm | g2 gen 1 firmware | cpe:2.3:o:qualcomm:g2_gen_1_firmware |
| qualcomm | g2 gen 1 | cpe:2.3:h:qualcomm:g2_gen_1 |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm ar8031 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 firmwareall versions
- qualcomm g1 gen 1 firmwareall versions
- qualcomm g2 gen 1 firmwareall versions
- qualcomm iq-615 firmwareall versions
- qualcomm iq-8275 firmwareall versions
- qualcomm iq-8300 firmwareall versions
- qualcomm iq-9075 firmwareall versions
- qualcomm iq-9100 firmwareall versions
- qualcomm lemans au lgit firmwareall versions
- qualcomm lemansau firmwareall versions
- qualcomm milos firmwareall versions
- qualcomm monaco iot firmwareall versions
- qualcomm netrani firmwareall versions
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 6200, FastConnect 6700, FastConnect 6900, FastConnect 7800, Flight RB5 5G Platform, G1 Gen 1, G2 Gen 1, IQ10 Series, IQ6 Series Platform, IQ8 Series Platform, IQ9 Series Platform, Kalpeni … (+28)affected
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-38422Nov 4, 2024 · Integer Overflow to Buffer Overflow in Audio31Monitor
- ← EarlierCVE-2025-47380Jan 7, 2026 · Untrusted Pointer Dereference in Camera31Monitor
- Later →CVE-2026-24075Sep 17, 2026 · Buffer Over-read in Qualcomm IPC28Monitor
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
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.