CVE Tools

Sd 212 Firmware

423 CVEs tracked. None of them is in CISA KEV.

This hub aggregates every CVE we track for Sd 212 Firmware, a product in the hardware firmware space. Use it to gauge the current risk picture and drill into individual advisories.

Sd 212 Firmware CVEs per month

Oct 2024 to Sep 2026. Point at a month, or focus the strip and use the arrow keys.
Sd 212 Firmware CVEs per month
MonthCVEs
2024-100
2024-115
2024-120
2025-010
2025-020
2025-030
2025-040
2025-050
2025-060
2025-070
2025-080
2025-090
2025-100
2025-110
2025-120
2026-010
2026-020
2026-030
2026-040
2026-050
2026-060
2026-070
2026-080
2026-090

Severity

How the 423 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.

  • Critical20148%
  • High17341%
  • Medium4912%

Latest CVEs

The 15 most recently published vulnerabilities affecting Sd 212 Firmware.

  1. CVE-2018-5852Buffer Over-read in IPA8.4
  2. CVE-2018-11952Improper Authentication in TrustZone8.4
  3. CVE-2018-11922Configurations in Android Build9.8
  4. CVE-2017-11076Use of Out-of-range Pointer Offset in Video9.8
  5. CVE-2017-9711Permissions, Privileges, and Access Controls in Data6.7
  6. CVE-2019-10520An unprivileged application can allocate GPU memory by calling memory allocation ioctl function and can exhaust all the memory which results in out of memory in Snapdragon Mobile, Snapdragon Voice ...5.5
  7. CVE-2019-10530Lack of check of data truncation on user supplied data in kernel leads to buffer overflow in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice...7.8
  8. CVE-2019-2332Memory corruption while accessing the memory as payload size is not validated before access in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Io...9.8
  9. CVE-2019-2325Out of boundary access due to token received from ADSP and is used without validation as an index into the array in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industri...9.8
  10. CVE-2019-2331Possible Integer overflow because of subtracting two integers without checking if the result would overflow or not in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Indust...9.8
  11. CVE-2019-2323Lack of check to ensure crypto engine data passed by user is initialized can result in bus error in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdrag...9.8
  12. CVE-2019-2324When ADSP is compromised, the audio port index that`s returned from ADSP might be out of the valid range and leads to out of boundary access in Snapdragon Auto, Snapdragon Connectivity, Snapdragon ...9.8
  13. CVE-2019-2285Out of bound write issue is observed while giving information about properties that have been set so far for playing video in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdrago...9.8
  14. CVE-2019-2283Improper validation of read and write index of tx and rx fifo`s before calculating pointer can lead to out-of-bound access in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdrago...9.8
  15. CVE-2019-2275While deserializing any key blob during key operations, buffer overflow could occur exposing partial key information if any key operations are invoked(Depends on CVE-2018-13907) in Snapdragon Auto,...5.5

Product grouping is registry-driven, with AI assist and human review. How it works

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store