7.8
CVE-2021-30263
- EPSS 0.04%
- Published 12.11.2021 07:15:07
- Last modified 21.11.2024 06:03:36
- Source product-security@qualcomm.com
- Teams watchlist Login
- Open Login
Possible race condition can occur due to lack of synchronization mechanism when On-Device Logging node open twice concurrently in Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music
Data is provided by the National Vulnerability Database (NVD)
Qualcomm ≫ Aqt1000 Firmware Version-
Qualcomm ≫ Ar8031 Firmware Version-
Qualcomm ≫ Ar8035 Firmware Version-
Qualcomm ≫ Csra6620 Firmware Version-
Qualcomm ≫ Csra6640 Firmware Version-
Qualcomm ≫ Qca6391 Firmware Version-
Qualcomm ≫ Qca6420 Firmware Version-
Qualcomm ≫ Qca6430 Firmware Version-
Qualcomm ≫ Qca8337 Firmware Version-
Qualcomm ≫ Qcm6125 Firmware Version-
Qualcomm ≫ Qcs405 Firmware Version-
Qualcomm ≫ Qcs6125 Firmware Version-
Qualcomm ≫ Sd 8c Firmware Version-
Qualcomm ≫ Sd 8cx Firmware Version-
Qualcomm ≫ Sd855 Firmware Version-
Qualcomm ≫ Sdx55 Firmware Version-
Qualcomm ≫ Sdx55m Firmware Version-
Qualcomm ≫ Wcd9335 Firmware Version-
Qualcomm ≫ Wcd9340 Firmware Version-
Qualcomm ≫ Wcd9341 Firmware Version-
Qualcomm ≫ Wcd9370 Firmware Version-
Qualcomm ≫ Wcn3950 Firmware Version-
Qualcomm ≫ Wcn3980 Firmware Version-
Qualcomm ≫ Wcn3998 Firmware Version-
Qualcomm ≫ Wcn3999 Firmware Version-
Qualcomm ≫ Wsa8810 Firmware Version-
Qualcomm ≫ Wsa8815 Firmware Version-
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
| Type | Source | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.04% | 0.088 |
| Source | 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
|
| nvd@nist.gov | 4.4 | 3.4 | 6.4 |
AV:L/AC:M/Au:N/C:P/I:P/A:P
|
| 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.