7.8
CVE-2025-21437
- EPSS 0.02%
- Veröffentlicht 07.04.2025 10:16:04
- Zuletzt bearbeitet 20.08.2025 21:12:59
- Quelle product-security@qualcomm.com
- Teams Watchlist Login
- Unerledigt Login
Memory corruption while processing memory map or unmap IOCTL operations simultaneously.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Qualcomm ≫ Qam8255p Firmware Version-
Qualcomm ≫ Qam8295p Firmware Version-
Qualcomm ≫ Qam8620p Firmware Version-
Qualcomm ≫ Qam8650p Firmware Version-
Qualcomm ≫ Qam8775p Firmware Version-
Qualcomm ≫ Qamsrv1h Firmware Version-
Qualcomm ≫ Qamsrv1m Firmware Version-
Qualcomm ≫ Qca6574 Firmware Version-
Qualcomm ≫ Qca6574a Firmware Version-
Qualcomm ≫ Qca6574au Firmware Version-
Qualcomm ≫ Qca6595 Firmware Version-
Qualcomm ≫ Qca6595au Firmware Version-
Qualcomm ≫ Qca6688aq Firmware Version-
Qualcomm ≫ Qca6696 Firmware Version-
Qualcomm ≫ Qca6698aq Firmware Version-
Qualcomm ≫ Qca6797aq Firmware Version-
Qualcomm ≫ Sa6155p Firmware Version-
Qualcomm ≫ Sa7255p Firmware Version-
Qualcomm ≫ Sa7775p Firmware Version-
Qualcomm ≫ Sa8155p Firmware Version-
Qualcomm ≫ Sa8195p Firmware Version-
Qualcomm ≫ Sa8255p Firmware Version-
Qualcomm ≫ Sa8295p Firmware Version-
Qualcomm ≫ Sa8620p Firmware Version-
Qualcomm ≫ Sa8650p Firmware Version-
Qualcomm ≫ Sa8770p Firmware Version-
Qualcomm ≫ Sa8775p Firmware Version-
Qualcomm ≫ Sa9000p Firmware Version-
Qualcomm ≫ Srv1h Firmware Version-
Qualcomm ≫ Srv1l Firmware Version-
Qualcomm ≫ Srv1m Firmware Version-
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
| Typ | Quelle | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.02% | 0.024 |
| Quelle | Base Score | Exploit Score | Impact Score | Vector String |
|---|---|---|---|---|
| product-security@qualcomm.com | 7.8 | 1.8 | 5.9 |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
|
CWE-416 Use After Free
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.