CVE-2025-47359: Use After Free in Secure Processor
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 multiple threads simultaneously access a memory free API.
- Published
- Feb 2, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 0th percentile
- CWE
- CWE-416
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 | qca6391 firmware | cpe:2.3:o:qualcomm:qca6391_firmware |
| qualcomm | qca6391 | cpe:2.3:h:qualcomm:qca6391 |
| qualcomm | qca6420 firmware | cpe:2.3:o:qualcomm:qca6420_firmware |
| qualcomm | qca6420 | cpe:2.3:h:qualcomm:qca6420 |
| qualcomm | qca6430 firmware | cpe:2.3:o:qualcomm:qca6430_firmware |
| qualcomm | qca6430 | cpe:2.3:h:qualcomm:qca6430 |
| qualcomm | qcc2072 firmware | cpe:2.3:o:qualcomm:qcc2072_firmware |
| qualcomm | qcc2072 | cpe:2.3:h:qualcomm:qcc2072 |
| qualcomm | sc8380xp firmware | cpe:2.3:o:qualcomm:sc8380xp_firmware |
| qualcomm | sc8380xp | cpe:2.3:h:qualcomm:sc8380xp |
| qualcomm | sc8180x-ad firmware | cpe:2.3:o:qualcomm:sc8180x-ad_firmware |
| qualcomm | sc8180x-ad | cpe:2.3:h:qualcomm:sc8180x-ad |
and 62 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm aqt1000 firmwareall versions
- qualcomm fastconnect 6200 firmwareall versions
- qualcomm fastconnect 6800 firmwareall versions
- qualcomm fastconnect 6900 firmwareall versions
- qualcomm fastconnect 7800 firmwareall versions
- qualcomm qca6391 firmwareall versions
- qualcomm qca6420 firmwareall versions
- qualcomm qca6430 firmwareall versions
- qualcomm qcc2072 firmwareall versions
- qualcomm sc8180x-aaab firmwareall versions
- qualcomm sc8180x-acaf firmwareall versions
- qualcomm sc8180x-ad firmwareall versions
- qualcomm sc8180xp-aaab firmwareall versions
- qualcomm sc8180xp-acaf firmwareall versions
- qualcomm sc8180xp-ad firmwareall versions
- qualcomm sc8280xp-abbb firmwareall versions
- qualcomm sc8380xp firmwareall versions
- qualcomm wcd9340 firmwareall versions
- qualcomm wcd9341 firmwareall versions
- qualcomm wcd9378c 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
- AQT1000, FastConnect 6200, FastConnect 6800, FastConnect 6900, FastConnect 7800, QCA6391, QCA6420, QCA6430, QCC2072, SC8380XP, Snapdragon 8c Compute Platform (SC8180X-AD) "Poipu Lite", Snapdragon 8c Compute Platform (SC8180XP-AD) "Poipu Lite" … (+25)affected
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-35134Due to insufficient validation of ELF headers, an Incorrect Calculation of Buffer Size can occur in Boot leading to memory corruption in Sna33Monitor
- CVE-2024-45570Use of Out-of-range Pointer Offset in Camera Driver31Monitor
- CVE-2024-43067Time-of-check Time-of-use (TOCTOU) Race Condition in Camera31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-21630Apr 13, 2023 · Integer Overflow in Multimedia Framework31Monitor
- ← EarlierCVE-2023-21655Sep 5, 2023 · Integer Overflow or Wraparound in Display31Monitor
- Later →CVE-2026-24085Jun 1, 2026 · Stack-based Buffer Overflow in Display28Monitor
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.
No history yet (it accumulates with the daily EPSS job).
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-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
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.