Show filters
178 Total Results
Displaying 11-20 of 178
Sort by:
Attacker Value
Unknown

CVE-2024-38408

Disclosure Date: November 04, 2024 (last updated November 09, 2024)
Cryptographic issue when a controller receives an LMP start encryption command under unexpected conditions.
Attacker Value
Unknown

CVE-2024-33032

Disclosure Date: November 04, 2024 (last updated November 08, 2024)
Memory corruption when the user application modifies the same shared memory asynchronously when kernel is accessing it.
Attacker Value
Unknown

CVE-2024-33069

Disclosure Date: October 07, 2024 (last updated October 17, 2024)
Transient DOS when transmission of management frame sent by host is not successful and error status is received in the host.
Attacker Value
Unknown

CVE-2024-23369

Disclosure Date: October 07, 2024 (last updated October 17, 2024)
Memory corruption when invalid length is provided from HLOS for FRS/UDS request/response buffers.
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.
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.
Attacker Value
Unknown

CVE-2024-33048

Disclosure Date: September 02, 2024 (last updated September 05, 2024)
Transient DOS while parsing the received TID-to-link mapping element of beacon/probe response frame.
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.
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.
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.