Show filters
125 Total Results
Displaying 11-20 of 125
Sort by:
Attacker Value
Unknown
CVE-2024-38425
Disclosure Date: October 07, 2024 (last updated October 17, 2024)
Information disclosure while sending implicit broadcast containing APP launch information.
0
Attacker Value
Unknown
CVE-2024-38402
Disclosure Date: September 02, 2024 (last updated September 06, 2024)
Memory corruption while processing IOCTL call for getting group info.
0
Attacker Value
Unknown
CVE-2024-33060
Disclosure Date: September 02, 2024 (last updated September 05, 2024)
Memory corruption when two threads try to map and unmap a single node simultaneously.
0
Attacker Value
Unknown
CVE-2024-33052
Disclosure Date: September 02, 2024 (last updated September 05, 2024)
Memory corruption when user provides data for FM HCI command control operations.
0
Attacker Value
Unknown
CVE-2024-33043
Disclosure Date: September 02, 2024 (last updated December 21, 2024)
Transient DOS while handling PS event when Program Service name length offset value is set to 255.
0
Attacker Value
Unknown
CVE-2024-33042
Disclosure Date: September 02, 2024 (last updated September 05, 2024)
Memory corruption when Alternative Frequency offset value is set to 255.
0
Attacker Value
Unknown
CVE-2024-33034
Disclosure Date: August 05, 2024 (last updated November 21, 2024)
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.
0
Attacker Value
Unknown
CVE-2024-33028
Disclosure Date: August 05, 2024 (last updated November 21, 2024)
Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released.
0
Attacker Value
Unknown
CVE-2024-33023
Disclosure Date: August 05, 2024 (last updated November 21, 2024)
Memory corruption while creating a fence to wait on timeline events, and simultaneously signal timeline events.
0
Attacker Value
Unknown
CVE-2024-33022
Disclosure Date: August 05, 2024 (last updated November 21, 2024)
Memory corruption while allocating memory in HGSL driver.
0
