Possible buffer over-read in windows wlan driver function due to lack of check of length of variable received from userspace in Snapdragon…

published 2020-04-16 6y ago modified 2026-06-17 4mo ago also EUVD-2020-24924

cvss: 9.1; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits: 0; none known

Possible buffer over-read in windows wlan driver function due to lack of check of length of variable received from userspace in Snapdragon Compute, Snapdragon Connectivity in MSM8998, QCA6390, SC7180, SC8180X, SDM850

Is CVE-2020-3653 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVD	2.0	9.4	AV:N/AC:L/Au:N/C:C/I:N/A:C

Affected products

Qualcomm, Inc. Snapdragon Compute, Snapdragon Connectivity

Classification

Weakness

CWE-20 Improper Input Validation
CWE-125 Out-of-bounds Read

References

qualcomm.com /company/product-security/bulletins/april-2020-bulletin
vendor-advisory

Sources

CVE List CVE-2020-3653
NVD CVE-2020-3653

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.