Qualcomm Sd820
182 CVEs affecting Qualcomm Sd820. Latest disclosed: 2025-11-04. Critical: 42, High: 123.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2023-22388 | Critical | 9.8 | 2023-11-07 | Memory Corruption in Multi-mode Call Processor while processing bit mask API. |
CVE-2022-40510 | Critical | 9.8 | 2023-08-08 | Memory corruption due to buffer copy without checking size of input in Audio while voice call with EVS vocoder. |
CVE-2022-25748 | Critical | 9.8 | 2022-10-19 | Memory corruption in WLAN due to integer overflow to buffer overflow while parsing GTK frames. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity… |
CVE-2022-25720 | Critical | 9.8 | 2022-10-19 | Memory corruption in WLAN due to out of bound array access during connect/roaming in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon C… |
CVE-2022-25651 | Critical | 9.8 | 2022-06-14 | Memory corruption in bluetooth host due to integer overflow while processing BT HFP-UNIT profile in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Indust… |
CVE-2021-1975 | Critical | 9.8 | 2021-11-12 | Possible heap overflow due to improper length check of domain while parsing the DNS response in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, S… |
CVE-2021-1920 | Critical | 9.8 | 2021-09-08 | Integer underflow can occur due to improper handling of incoming RTCP packets in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consu… |
CVE-2021-1919 | Critical | 9.8 | 2021-09-08 | Integer underflow can occur when the RTCP length is lesser than than the actual blocks present in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity… |
CVE-2021-1916 | Critical | 9.8 | 2021-09-08 | Possible buffer underflow due to lack of check for negative indices values when processing user provided input in Snapdragon Auto, Snapdragon Compute, Snapdrag… |
CVE-2020-11299 | Critical | 9.8 | 2021-03-17 | Buffer overflow can occur in video while playing the non-standard clip in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT… |
CVE-2020-11227 | Critical | 9.8 | 2021-03-17 | Out of bound write while parsing RTT/TTY packet parsing due to lack of check of buffer size before copying into buffer in Snapdragon Auto, Snapdragon Compute… |
CVE-2020-11283 | Critical | 9.8 | 2021-02-22 | A buffer overflow can occur when playing an MKV clip due to lack of input validation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdrago… |
CVE-2020-11272 | Critical | 9.8 | 2021-02-22 | Before enqueuing a frame to the PE queue for further processing, an entry in a hash table can be deleted and using a stale version later can lead to use after… |
CVE-2020-11170 | Critical | 9.8 | 2021-02-22 | Out of bound memory access while playing music playbacks with crafted vorbis content due to improper checks in header extraction in Snapdragon Auto, Snapdragon… |
CVE-2020-3691 | Critical | 9.8 | 2021-01-21 | Possible out of bound memory access in audio due to integer underflow while processing modified contents in Snapdragon Auto, Snapdragon Compute, Snapdragon Con… |
CVE-2020-3686 | Critical | 9.8 | 2021-01-21 | Possible memory out of bound issue during music playback when an incorrect bit stream content is copied into array without checking the length of array in Snap… |
CVE-2020-11216 | Critical | 9.8 | 2021-01-21 | Buffer over read can happen in video driver when playing clip with atomsize having value UINT32_MAX in Snapdragon Auto, Snapdragon Compute, Snapdragon Connecti… |
CVE-2020-11213 | Critical | 9.8 | 2021-01-21 | Out of bound reads might occur in while processing Service descriptor due to improper validation of length of fields in Snapdragon Auto, Snapdragon Compute, Sn… |
CVE-2020-11212 | Critical | 9.8 | 2021-01-21 | Out of bounds reads while parsing NAN beacons attributes and OUIs due to improper length of field check in Snapdragon Auto, Snapdragon Compute, Snapdragon Conn… |
CVE-2020-11197 | Critical | 9.8 | 2021-01-21 | Possible integer overflow can occur when stream info update is called when total number of streams detected are zero while parsing TS clip with invalid data in… |