Qam8295p vulnerabilitiesAnd the versions its exploited flaws hit.

Product4 known exploited0 versions
The short answer

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

Check your version

The most recent Qam8295p flaw added to the known-exploited list is CVE-2024-43047, on 8 October 2024. We keep watching the known-exploited list.

Other names

Is Qam8295p listed under other names? Yes.

Qualcomm also lists Qam8295p under more specific names, such as Qam8295p 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 Qam8295p 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 Qam8295p vulnerabilities are being exploited?

4 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.8
    CVE-2024-43047HighKnown exploited
    Qualcomm Multiple Chipsets Use-After-Free Vulnerability

    Multiple Qualcomm chipsets contain a use-after-free vulnerability due to memory corruption in DSP Services while maintaining memory maps of HLOS memory.

    Chance of use0.7%Known exploited since8 Oct 2024
  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-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
  4. 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
Exploit likelihood

Which Qam8295p 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. 1.3%

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

    CVSS7.8Published6 Jun 2023
  2. 0.9%

    Memory corruption in Core due to stack-based buffer overflow.

    CVSS8.4Published9 Jan 2023
  3. 0.8%

    Possible buffer overflow due to improper parsing of headers while playing the FLAC audio clip in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT,...

    CVSS9.8Published14 Jun 2022
  4. 0.8%

    Denial of service in WLAN due to out-of-bound read happens while processing VHT action frame in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon...

    CVSS7.5Published19 Oct 2022
  5. 0.8%
    CVE-2023-33106HighKnown exploited

    Memory corruption while submitting a large list of sync points in an AUX command to the IOCTL_KGSL_GPU_AUX_COMMAND.

    CVSS8.4Published5 Dec 2023
  6. 0.7%
    CVE-2023-33107HighKnown exploited

    Memory corruption in Graphics Linux while assigning shared virtual memory region during IOCTL call.

    CVSS8.4Published5 Dec 2023
  7. 0.7%

    Memory corruption due to stack-based buffer overflow in Core

    CVSS8.4Published9 Jan 2023
  8. 0.7%
    CVE-2023-33063HighKnown exploited

    Memory corruption in DSP Services during a remote call from HLOS to DSP.

    CVSS7.8Published5 Dec 2023
  9. 0.7%
    CVE-2024-43047HighKnown exploited

    Memory corruption while maintaining memory maps of HLOS memory.

    CVSS7.8Published7 Oct 2024
  10. 0.6%

    Memory corruption while parsing the ML IE due to invalid frame content.

    CVSS9.8Published3 Feb 2025
Precursor Intelligence

Running Qam8295p? 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 396 published vulnerabilities listed under the name Qam8295p, across 0 versions. The most recent Qam8295p flaw added to the known-exploited list is CVE-2024-43047, on 8 October 2024.

4 are on the list of flaws known to be exploited. The most recently added are CVE-2024-43047, CVE-2023-33063 and CVE-2023-33106.

Qualcomm also lists Qam8295p under more specific names, such as Qam8295p 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 Qam8295p. 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.