7.8

CVE-2020-11124

u'Possible use-after-free while accessing diag client map table since list can be reallocated due to exceeding max client limit.' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music in MDM9607, Nicobar, QCS404, QCS405, QCS610, Rennell, SA6155P, SA8155P, Saipan, SC8180X, SDM660, SDX55, SM6150, SM7150, SM8150, SM8250, SXR2130

Data is provided by the National Vulnerability Database (NVD)
Qualcomm ≫ Mdm9607 Firmware Version-
   Qualcomm ≫ Mdm9607 Version-
Qualcomm ≫ Nicobar Firmware Version-
   Qualcomm ≫ Nicobar Version-
Qualcomm ≫ Qcs404 Firmware Version-
   Qualcomm ≫ Qcs404 Version-
Qualcomm ≫ Qcs405 Firmware Version-
   Qualcomm ≫ Qcs405 Version-
Qualcomm ≫ Qcs610 Firmware Version-
   Qualcomm ≫ Qcs610 Version-
Qualcomm ≫ Rennell Firmware Version-
   Qualcomm ≫ Rennell Version-
Qualcomm ≫ Sa6155p Firmware Version-
   Qualcomm ≫ Sa6155p Version-
Qualcomm ≫ Sa8155p Firmware Version-
   Qualcomm ≫ Sa8155p Version-
Qualcomm ≫ Saipan Firmware Version-
   Qualcomm ≫ Saipan Version-
Qualcomm ≫ Sc8180x Firmware Version-
   Qualcomm ≫ Sc8180x Version-
Qualcomm ≫ Sdm660 Firmware Version-
   Qualcomm ≫ Sdm660 Version-
Qualcomm ≫ Sdx55 Firmware Version-
   Qualcomm ≫ Sdx55 Version-
Qualcomm ≫ Sm6150 Firmware Version-
   Qualcomm ≫ Sm6150 Version-
Qualcomm ≫ Sm7150 Firmware Version-
   Qualcomm ≫ Sm7150 Version-
Qualcomm ≫ Sm8150 Firmware Version-
   Qualcomm ≫ Sm8150 Version-
Qualcomm ≫ Sm8250 Firmware Version-
   Qualcomm ≫ Sm8250 Version-
Qualcomm ≫ Sxr2130 Firmware Version-
   Qualcomm ≫ Sxr2130 Version-
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
EPSS Metriken
Type Source Score Percentile
EPSS FIRST.org 0.04% 0.077
CVSS Metriken
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 7.2 3.9 10
AV:L/AC:L/Au:N/C:C/I:C/A:C
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.