Show filters
187 Total Results
Displaying 21-30 of 187
Sort by:
Attacker Value
Unknown
CVE-2024-33049
Disclosure Date: October 07, 2024 (last updated October 17, 2024)
Transient DOS while parsing noninheritance IE of Extension element when length of IE is 2 of beacon frame.
0
Attacker Value
Unknown
CVE-2024-23376
Disclosure Date: October 07, 2024 (last updated October 17, 2024)
Memory corruption while sending the persist buffer command packet from the user-space to the kernel space through the IOCTL call.
0
Attacker Value
Unknown
CVE-2024-23375
Disclosure Date: October 07, 2024 (last updated October 17, 2024)
Memory corruption during the network scan request.
0
Attacker Value
Unknown
CVE-2024-23374
Disclosure Date: October 07, 2024 (last updated October 17, 2024)
Memory corruption is possible when an attempt is made from userspace or console to write some haptics effects pattern to the haptics debugfs file.
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-38401
Disclosure Date: September 02, 2024 (last updated September 05, 2024)
Memory corruption while processing concurrent IOCTL calls.
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-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-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
