Csra6620 vulnerabilitiesAnd the versions its exploited flaws hit.

Product8 known exploited0 versions
The short answer

Csra6620 is made by Qualcomm. We track 427 published vulnerabilities listed under that exact name, across 0 versions. 8 of them are on the list of flaws known to be exploited, the newest added on 3 June 2025. Qualcomm lists newer releases under their own names, such as Csra6620 Firmware, so check those pages too.

Check your version

The most recent Csra6620 flaw added to the known-exploited list is CVE-2025-27038, on 3 June 2025. We keep watching the known-exploited list.

Other names

Is Csra6620 listed under other names? Yes.

Qualcomm also lists Csra6620 under more specific names, such as Csra6620 Firmware. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Versions

Which versions of Csra6620 do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

Known exploited

Which Csra6620 vulnerabilities are being exploited?

8 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.5
    CVE-2025-27038HighKnown exploited
    Qualcomm Multiple Chipsets Use-After-Free Vulnerability

    Multiple Qualcomm chipsets contain a use-after-free vulnerability.

    Chance of use1.0%Known exploited since3 Jun 2025
  2. 7.8
    CVE-2023-33063HighKnown exploited
    Qualcomm Multiple Chipsets Use-After-Free Vulnerability

    Multiple Qualcomm chipsets contain a use-after-free vulnerability due to memory corruption in DSP Services during a remote call from HLOS to DSP.

    Chance of use0.7%Known exploited since5 Dec 2023
  3. 8.4
    CVE-2022-22071HighKnown exploited
    Qualcomm Multiple Chipsets Use-After-Free Vulnerability

    Multiple Qualcomm chipsets contain a use-after-free vulnerability when process shell memory is freed using IOCTL munmap call and process initialization is in progress.

    Chance of use0.4%Known exploited since5 Dec 2023
  4. 8.4
    CVE-2023-33106HighKnown exploited
    Qualcomm Multiple Chipsets Use of Out-of-Range Pointer Offset Vulnerability

    Multiple Qualcomm chipsets contain a use of out-of-range pointer offset vulnerability due to memory corruption in Graphics while submitting a large list of sync points in an AUX command to the IOCTL_KGSL_GPU_AUX_COMMAND.

    Chance of use0.8%Known exploited since5 Dec 2023
  5. 8.4
    CVE-2023-33107HighKnown exploited
    Qualcomm Multiple Chipsets Integer Overflow Vulnerability

    Multiple Qualcomm chipsets contain an integer overflow vulnerability due to memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call.

    Chance of use0.7%Known exploited since5 Dec 2023
  6. 7.8
    CVE-2020-11261HighKnown exploited
    Qualcomm Multiple Chipsets Improper Input Validation Vulnerability

    Memory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,...

    Chance of use1.6%Known exploited since1 Dec 2021
  7. 6.2
    CVE-2021-1906MediumKnown exploited
    Qualcomm Multiple Chipsets Detection of Error Condition Without Action Vulnerability

    Multiple Qualcomm chipsets contain a detection of error condition without action vulnerability when improper handling of address deregistration on failure can lead to new GPU address allocation failure.

    Chance of use0.5%Known exploited since3 Nov 2021
  8. 8.4
    CVE-2021-1905HighKnown exploited
    Qualcomm Multiple Chipsets Use-After-Free Vulnerability

    Multiple Qualcomm Chipsets contain a use after free vulnerability due to improper handling of memory mapping of multiple processes simultaneously.

    Chance of use1.5%Known exploited since3 Nov 2021
Exploit likelihood

Which Csra6620 flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 13%

    Improper authentication of Non-EAPOL/WAPI plaintext frames during four-way handshake can lead to arbitrary network packet injection in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer...

    CVSS9.8Published8 Sep 2021
  2. 11%

    Improper authentication of un-encrypted plaintext Wi-Fi frames in an encrypted network can lead to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer...

    CVSS7.5Published8 Sep 2021
  3. 4.0%

    An out of bound memory access can occur due to improper validation of number of frames being passed during music playback in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,...

    CVSS9.8Published3 Jan 2022
  4. 1.6%
    CVE-2020-11261HighKnown exploited

    Memory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT,...

    CVSS7.8Published9 Jun 2021
  5. 1.5%
    CVE-2021-1905HighKnown exploited

    Possible use after free due to improper handling of memory mapping of multiple processes simultaneously.

    CVSS8.4Published7 May 2021
  6. 1.4%

    Improper validation of program headers containing ELF metadata can lead to image verification bypass in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity,...

    CVSS7.8Published11 Feb 2022
  7. 1.3%

    Memory corruption due to double free in Core while mapping HLOS address to the list.

    CVSS7.8Published6 Jun 2023
  8. 1.2%

    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 Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity,...

    CVSS9.8Published21 Jan 2021
  9. 1.1%

    Out of bound access in WLAN driver due to lack of validation of array length before copying into array in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity,...

    CVSS9.8Published21 Jan 2021
  10. 1.1%

    Uninitialized pointers accessed during music play back with incorrect bit stream due to an uninitialized heap memory result in instability in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon...

    CVSS9.8Published21 Jan 2021
Precursor Intelligence

Running Csra6620? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 427 published vulnerabilities listed under the name Csra6620, across 0 versions. The most recent Csra6620 flaw added to the known-exploited list is CVE-2025-27038, on 3 June 2025.

8 are on the list of flaws known to be exploited. The most recently added are CVE-2025-27038, CVE-2023-33063 and CVE-2022-22071.

Qualcomm also lists Csra6620 under more specific names, such as Csra6620 Firmware. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a Precursor Intelligence account and track Csra6620. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.