CVE-2025-21436: Use After Free in DSP Service
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 may occur while initiating two IOCTL calls simultaneously to create processes from two different threads.
- Published
- Apr 7, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 1th 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 | fastconnect 7800 firmware | cpe:2.3:o:qualcomm:fastconnect_7800_firmware |
| qualcomm | fastconnect 7800 | cpe:2.3:h:qualcomm:fastconnect_7800 |
| qualcomm | qmp1000 firmware | cpe:2.3:o:qualcomm:qmp1000_firmware |
| qualcomm | qmp1000 | cpe:2.3:h:qualcomm:qmp1000 |
| qualcomm | sm8735 firmware | cpe:2.3:o:qualcomm:sm8735_firmware |
| qualcomm | sm8735 | cpe:2.3:h:qualcomm:sm8735 |
| qualcomm | sm8750 firmware | cpe:2.3:o:qualcomm:sm8750_firmware |
| qualcomm | sm8750 | cpe:2.3:h:qualcomm:sm8750 |
| qualcomm | sm8750p firmware | cpe:2.3:o:qualcomm:sm8750p_firmware |
| qualcomm | sm8750p | cpe:2.3:h:qualcomm:sm8750p |
| qualcomm | snapdragon 8 gen 3 mobile platform firmware | cpe:2.3:o:qualcomm:snapdragon_8_gen_3_mobile_platform_firmware |
| qualcomm | snapdragon 8 gen 3 mobile platform | cpe:2.3:h:qualcomm:snapdragon_8_gen_3_mobile_platform |
and 38 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 7800, QMP1000, SM8735, SM8750, SM8750P, Snapdragon 8 Gen 3 Mobile Platform, Snapdragon W5+ Gen 1 Wearable Platform, SW5100, SW5100P, SXR2330P, WCD9378, WCD9380 … (+13)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 7800 firmwareall versions
- qualcomm qmp1000 firmwareall versions
- qualcomm sm8735 firmwareall versions
- qualcomm sm8750 firmwareall versions
- qualcomm sm8750p firmwareall versions
- qualcomm snapdragon 8 gen 3 mobile platform firmwareall versions
- qualcomm snapdragon w5+ gen 1 wearable platform firmwareall versions
- qualcomm sw5100 firmwareall versions
- qualcomm sw5100p firmwareall versions
- qualcomm sxr2330p firmwareall versions
- qualcomm wcd9378 firmwareall versions
- qualcomm wcd9380 firmwareall versions
- qualcomm wcd9390 firmwareall versions
- qualcomm wcd9395 firmwareall versions
- qualcomm wcn7750 firmwareall versions
- qualcomm wcn7860 firmwareall versions
- qualcomm wcn7861 firmwareall versions
- qualcomm wcn7880 firmwareall versions
- qualcomm wcn7881 firmwareall versions
- qualcomm wsa8830 firmwareall versions
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-47373Out-of-bounds Write in Automotive31Monitor
- CVE-2025-47352Improper Validation of Array Index in Audio31Monitor
- CVE-2025-47329Release of Invalid Pointer or Reference in Android Core31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-53025Mar 3, 2025 · Integer Overflow or Wraparound in BT Controller22Monitor
- ← EarlierCVE-2024-43065Apr 7, 2025 · Exposed Dangerous Method or Function in HLOS28Monitor
- Later →CVE-2025-21441Apr 7, 2025 · Out-of-bounds Read in Windows WLAN Host31Monitor
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-4558329 days apartUse After Free in Secure Processor31Monitor
- CVE-2024-3841263 days apartUse After Free in Computer Vision31Monitor
- CVE-2025-2705692 days apartUse After Free in DSP Service31Monitor
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.