Show filters
553 Total Results
Displaying 21-30 of 553
Sort by:
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-33051
Disclosure Date: September 02, 2024 (last updated September 05, 2024)
Transient DOS while processing TIM IE from beacon frame as there is no check for IE length.
0
Attacker Value
Unknown
CVE-2024-33050
Disclosure Date: September 02, 2024 (last updated September 05, 2024)
Transient DOS while parsing MBSSID during new IE generation in beacon/probe frame when IE length check is either missing or improper.
0
Attacker Value
Unknown
CVE-2024-33045
Disclosure Date: September 02, 2024 (last updated September 05, 2024)
Memory corruption when BTFM client sends new messages over Slimbus to ADSP.
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-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-33027
Disclosure Date: August 05, 2024 (last updated November 21, 2024)
Memory corruption can occur when arbitrary user-space app gains kernel level privilege to modify DDR memory by corrupting the GPU page table.
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
