Qualcomm Snapdragon Auto up to SRV1M ELF Image buffer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Qualcomm Snapdragon Auto. Affected is an unknown function of the component ELF Image Handler. Performing a manipulation results in buffer overflow. This vulnerability is cataloged as CVE-2025-47372. The attack must be initiated from a local position. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Qualcomm Snapdragon Auto. This affects an unknown functionality of the component ELF Image Handler. The manipulation with an unknown input leads to a buffer overflow vulnerability. CWE is classifying the issue as CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Memory Corruption when a corrupted ELF image with an oversized file size is read into a buffer without authentication.
The advisory is shared at docs.qualcomm.com. This vulnerability is uniquely identified as CVE-2025-47372 since 05/06/2025. The exploitability is told to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/24/2025).
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-2711). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Lenovo BIOS
- Lenovo Computer
- Google Android
Product
Type
Vendor
Name
Version
- QAM8255P
- QAM8620P
- QAM8650P
- QAM8775P
- QAMSRV1H
- QAMSRV1M
- QCA6595
- QCA6595AU
- QCA6678AQ
- QCA6696
- QCA6698AQ
- QCA6797AQ
- SA7255P
- SA7775P
- SA8255P
- SA8620P
- SA8650P
- SA8770P
- SA8775P
- SA9000P
- SRV1H
- SRV1L
- SRV1M
License
Website
- Vendor: https://www.qualcomm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.4VulDB Meta Temp Score: 8.3
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.4
NVD Vector: 🔒
CNA Base Score: 9.0
CNA Vector (qualcomm): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Buffer overflowCWE: CWE-120 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
05/06/2025 CVE reserved12/18/2025 Advisory disclosed
12/18/2025 VulDB entry created
12/24/2025 VulDB entry last update
Sources
Vendor: qualcomm.comAdvisory: docs.qualcomm.com
Status: Confirmed
CVE: CVE-2025-47372 (🔒)
GCVE (CVE): GCVE-0-2025-47372
GCVE (VulDB): GCVE-100-337149
CERT Bund: WID-SEC-2025-2711 - Android Patchday Dezember 2025: Mehrere Schwachstellen
Entry
Created: 12/18/2025 08:48Updated: 12/24/2025 09:09
Changes: 12/18/2025 08:48 (64), 12/21/2025 13:02 (7), 12/24/2025 09:09 (10)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.