Show filters
727 Total Results
Displaying 1-10 of 727
Sort by:
Attacker Value
Unknown
CVE-2024-49839
Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Memory corruption during management frame processing due to mismatch in T2LM info element.
0
Attacker Value
Unknown
CVE-2024-49838
Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Information disclosure while parsing the OCI IE with invalid length.
0
Attacker Value
Unknown
CVE-2024-45584
Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Memory corruption can occur when a compat IOCTL call is followed by a normal IOCTL call from userspace.
0
Attacker Value
Unknown
CVE-2024-45571
Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Memory corruption may occour occur when stopping the WLAN interface after processing a WMI command from the interface.
0
Attacker Value
Unknown
CVE-2024-45569
Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Memory corruption while parsing the ML IE due to invalid frame content.
0
Attacker Value
Unknown
CVE-2024-38420
Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Memory corruption while configuring a Hypervisor based input virtual device.
0
Attacker Value
Unknown
CVE-2024-38416
Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Information disclosure during audio playback.
0
Attacker Value
Unknown
CVE-2024-45558
Disclosure Date: January 06, 2025 (last updated January 14, 2025)
Transient DOS can occur when the driver parses the per STA profile IE and tries to access the EXTN element ID without checking the IE length.
0
Attacker Value
Unknown
CVE-2024-45555
Disclosure Date: January 06, 2025 (last updated January 14, 2025)
Memory corruption can occur if an already verified IFS2 image is overwritten, bypassing boot verification. This allows unauthorized programs to be injected into security-sensitive images, enabling the booting of a tampered IFS2 system image.
0
Attacker Value
Unknown
CVE-2024-45553
Disclosure Date: January 06, 2025 (last updated January 14, 2025)
Memory corruption can occur when process-specific maps are added to the global list. If a map is removed from the global list while another thread is using it for a process-specific task, issues may arise.
0