VYPR

Qcs8250 Firmware

by Qualcomm

CVEs (106)

  • CVE-2023-33107HigKEVDec 5, 2023
    risk 0.67cvss 8.4epss 0.01

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

  • CVE-2023-33106HigKEVDec 5, 2023
    risk 0.67cvss 8.4epss 0.01

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

  • CVE-2023-43552CriMar 4, 2024
    risk 0.64cvss 9.8epss 0.00

    Memory corruption while processing MBSSID beacon containing several subelement IE.

  • CVE-2023-43556CriJun 3, 2024
    risk 0.60cvss 9.3epss 0.00

    Memory corruption in Hypervisor when platform information mentioned is not aligned.

  • CVE-2023-28578CriMar 4, 2024
    risk 0.60cvss 9.3epss 0.00

    Memory corruption in Core Services while executing the command for removing a single event listener.

  • CVE-2023-33072CriFeb 6, 2024
    risk 0.60cvss 9.3epss 0.00

    Memory corruption in Core while processing control functions.

  • CVE-2023-33030CriJan 2, 2024
    risk 0.60cvss 9.3epss 0.00

    Memory corruption in HLOS while running playready use-case.

  • CVE-2023-33054CriDec 5, 2023
    risk 0.59cvss 9.1epss 0.00

    Cryptographic issue in GPS HLOS Driver while downloading Qualcomm GNSS assistance data.

  • CVE-2023-21673HigOct 3, 2023
    risk 0.57cvss 8.7epss 0.00

    Improper Access to the VM resource manager can lead to Memory Corruption.

  • CVE-2023-43534HigFeb 6, 2024
    risk 0.56cvss 8.6epss 0.00

    Memory corruption while validating the TID to Link Mapping action request frame, when a station connects to an access point.

  • CVE-2023-43520HigFeb 6, 2024
    risk 0.56cvss 8.6epss 0.00

    Memory corruption when AP includes TID to link mapping IE in the beacons and STA is parsing the beacon TID to link mapping IE.

  • CVE-2024-33056HigDec 2, 2024
    risk 0.55cvss 8.4epss 0.00

    Memory corruption when allocating and accessing an entry in an SMEM partition continuously.

  • CVE-2024-33034HigAug 5, 2024
    risk 0.55cvss 8.4epss 0.00

    Memory corruption can occur if VBOs hold outdated or invalid GPU SMMU mappings, especially when the binding and reclaiming of memory buffers are performed at the same time.

  • CVE-2024-33028HigAug 5, 2024
    risk 0.55cvss 8.4epss 0.00

    Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released.

  • CVE-2024-23383HigAug 5, 2024
    risk 0.55cvss 8.4epss 0.00

    Memory corruption when kernel driver attempts to trigger hardware fences.

  • CVE-2024-23381HigAug 5, 2024
    risk 0.55cvss 8.4epss 0.00

    Memory corruption when memory mapped in a VBO is not unmapped by the GPU SMMU.

  • CVE-2024-23373HigJul 1, 2024
    risk 0.55cvss 8.4epss 0.00

    Memory corruption when IOMMU unmap operation fails, the DMA and anon buffers are getting released.

  • CVE-2024-23372HigJul 1, 2024
    risk 0.55cvss 8.4epss 0.00

    Memory corruption while invoking IOCTL call for GPU memory allocation and size param is greater than expected size.

  • CVE-2024-23351HigMay 6, 2024
    risk 0.55cvss 8.4epss 0.00

    Memory corruption as GPU registers beyond the last protected range can be accessed through LPAC submissions.

  • CVE-2024-21471HigMay 6, 2024
    risk 0.55cvss 8.4epss 0.00

    Memory corruption when IOMMU unmap of a GPU buffer fails in Linux.

Page 1 of 6