7.8
CVE-2023-43544
- EPSS 0.03%
- Veröffentlicht 03.06.2024 10:15:10
- Zuletzt bearbeitet 27.01.2025 19:11:15
- Quelle product-security@qualcomm.com
- Teams Watchlist Login
- Unerledigt Login
Memory corruption when IPC callback handle is used after it has been released during register callback by another thread.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Qualcomm ≫ Ar8035 Firmware Version-
Qualcomm ≫ Fastconnect 7800 Firmware Version-
Qualcomm ≫ Qam8255p Firmware Version-
Qualcomm ≫ Qam8775p Firmware Version-
Qualcomm ≫ Qca6584au Firmware Version-
Qualcomm ≫ Qca6698aq Firmware Version-
Qualcomm ≫ Qca8081 Firmware Version-
Qualcomm ≫ Qca8337 Firmware Version-
Qualcomm ≫ Qcc710 Firmware Version-
Qualcomm ≫ Qcn6224 Firmware Version-
Qualcomm ≫ Qcn6274 Firmware Version-
Qualcomm ≫ Qfw7114 Firmware Version-
Qualcomm ≫ Qfw7124 Firmware Version-
Qualcomm ≫ Sa8255p Firmware Version-
Qualcomm ≫ Sa8770p Firmware Version-
Qualcomm ≫ Sa8775p Firmware Version-
Qualcomm ≫ Sa9000p Firmware Version-
Qualcomm ≫ Snapdragon W5+ Gen 1 Wearable Firmware Version-
Qualcomm ≫ Snapdragon X75 5g Modem-rf Firmware Version-
Qualcomm ≫ Sw5100 Firmware Version-
Qualcomm ≫ Sw5100p Firmware Version-
Qualcomm ≫ Wcd9340 Firmware Version-
Qualcomm ≫ Wcn3980 Firmware Version-
Qualcomm ≫ Wcn3988 Firmware Version-
Qualcomm ≫ Wsa8830 Firmware Version-
Qualcomm ≫ Wsa8835 Firmware Version-
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Typ | Quelle | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 0.03% | 0.06 |
Quelle | Base Score | Exploit Score | Impact Score | Vector String |
---|---|---|---|---|
nvd@nist.gov | 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
|
product-security@qualcomm.com | 6.7 | 0.8 | 5.9 |
CVSS:3.1/AV:L/AC:L/PR:H/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.