Page 5 of 59 results (0.010 seconds)

CVSS: 8.4EPSS: 0%CPEs: 4EXPL: 0

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. • https://docs.qualcomm.com/product/publicresources/securitybulletin/august-2024-bulletin.html • CWE-416: Use After Free •

CVSS: 8.4EPSS: 0%CPEs: 4EXPL: 0

Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released. • https://docs.qualcomm.com/product/publicresources/securitybulletin/august-2024-bulletin.html • CWE-416: Use After Free •

CVSS: 8.4EPSS: 0%CPEs: 19EXPL: 0

Memory corruption can occur when arbitrary user-space app gains kernel level privilege to modify DDR memory by corrupting the GPU page table. • https://docs.qualcomm.com/product/publicresources/securitybulletin/august-2024-bulletin.html • CWE-284: Improper Access Control •

CVSS: 8.4EPSS: 0%CPEs: 7EXPL: 0

Memory corruption while creating a fence to wait on timeline events, and simultaneously signal timeline events. • https://docs.qualcomm.com/product/publicresources/securitybulletin/august-2024-bulletin.html • CWE-416: Use After Free •

CVSS: 8.4EPSS: 0%CPEs: 3EXPL: 0

Memory corruption while allocating memory in HGSL driver. • https://docs.qualcomm.com/product/publicresources/securitybulletin/august-2024-bulletin.html • CWE-190: Integer Overflow or Wraparound •