CVE-2020-3640

u'Resizing the usage table header before passing all the checks leads to the function exiting with a usage table in invalid state when a HLOS adversary calls the function with wrong input' in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in Bitra, Kamorta, QCS404, QCS610, Rennell, Saipan, SC7180, SDX55, SM6150, SM7150, SM8250, SXR2130

Published: 2020-09-08 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-3640 is rated Low Risk (34.9/100): CVSS High severity, with low exploitation likelihood (EPSS 0.20%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-3640

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.09% 0.20% +0.11%
2 2026-01-13 0.03% 0.09% +0.06%
3 2025-03-30 — 0.03% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-3640

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
7.2 2.0 HIGH
AV:L/AC:L/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 3.9 10.0 [email protected]

Weakness enumeration for CVE-2020-3640

Affected software / configurations for CVE-2020-3640

Vendor Product Version Raw CPE
qualcomm bitra_firmware — cpe:2.3:o:qualcomm:bitra_firmware:-:*:*:*:*:*:*:*
qualcomm kamorta_firmware — cpe:2.3:o:qualcomm:kamorta_firmware:-:*:*:*:*:*:*:*
qualcomm qcs404_firmware — cpe:2.3:o:qualcomm:qcs404_firmware:-:*:*:*:*:*:*:*
qualcomm qcs610_firmware — cpe:2.3:o:qualcomm:qcs610_firmware:-:*:*:*:*:*:*:*
qualcomm rennell_firmware — cpe:2.3:o:qualcomm:rennell_firmware:-:*:*:*:*:*:*:*
qualcomm saipan_firmware — cpe:2.3:o:qualcomm:saipan_firmware:-:*:*:*:*:*:*:*
qualcomm sc7180_firmware — cpe:2.3:o:qualcomm:sc7180_firmware:-:*:*:*:*:*:*:*
qualcomm sdx55_firmware — cpe:2.3:o:qualcomm:sdx55_firmware:-:*:*:*:*:*:*:*
qualcomm sm6150_firmware — cpe:2.3:o:qualcomm:sm6150_firmware:-:*:*:*:*:*:*:*
qualcomm sm7150_firmware — cpe:2.3:o:qualcomm:sm7150_firmware:-:*:*:*:*:*:*:*
qualcomm sm8250_firmware — cpe:2.3:o:qualcomm:sm8250_firmware:-:*:*:*:*:*:*:*
qualcomm sxr2130_firmware — cpe:2.3:o:qualcomm:sxr2130_firmware:-:*:*:*:*:*:*:*

References for CVE-2020-3640

cvelogic Threat Intelligence