CVE-2025-47374
Received
Received - Intake
Use-After-Free Memory Corruption in Qualcomm Signal Handling
Publication date: 2026-04-06
Last updated on: 2026-04-08
Assigner: Qualcomm, Inc.
Description
Description
Memory Corruption when accessing freed memory due to concurrent fence deregistration and signal handling.
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| qualcomm | fastconnect_6900_firmware | * |
| qualcomm | fastconnect_7800_firmware | * |
| qualcomm | pandeiro_firmware | * |
| qualcomm | qln1083bd_firmware | * |
| qualcomm | qln1086bd_firmware | * |
| qualcomm | qpa1083bd_firmware | * |
| qualcomm | qpa1086bd_firmware | * |
| qualcomm | qxm1083_firmware | * |
| qualcomm | qxm1086_firmware | * |
| qualcomm | qxm1093_firmware | * |
| qualcomm | qxm1094_firmware | * |
| qualcomm | qxm1095_firmware | * |
| qualcomm | qxm1096_firmware | * |
| qualcomm | sar1165p_firmware | * |
| qualcomm | sar2130p_firmware | * |
| qualcomm | snapdragon_ar1_gen_1_platform_firmware | * |
| qualcomm | snapdragon_ar1+_gen_1_platform_firmware | * |
| qualcomm | sxr2230p_firmware | * |
| qualcomm | sxr2250p_firmware | * |
| qualcomm | sxr2330p_firmware | * |
| qualcomm | sxr2350p_firmware | * |
| qualcomm | wcd9380_firmware | * |
| qualcomm | wcd9385_firmware | * |
| qualcomm | wcn7860_firmware | * |
| qualcomm | wcn7861_firmware | * |
| qualcomm | wsa8830_firmware | * |
| qualcomm | wsa8832_firmware | * |
| qualcomm | wsa8835_firmware | * |
| qualcomm | xrv7209_firmware | * |
| qualcomm | xrv9209_firmware | * |
Helpful Resources
Exploitability
CWE
KEV
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a memory corruption issue that occurs when accessing memory that has already been freed. It happens due to concurrent operations involving fence deregistration and signal handling.
How can this vulnerability impact me? :
The vulnerability can lead to memory corruption which may result in unauthorized modification of data (integrity impact), disruption of service (availability impact), and potential leakage or exposure of information (confidentiality impact).
Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70