Show filters
204 Total Results
Displaying 1-10 of 204
Sort by:
Attacker Value
Unknown
CVE-2024-49843
Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Memory corruption while processing IOCTL from user space to handle GPU AHB bus error.
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-49834
Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Memory corruption while power-up or power-down sequence of the camera sensor.
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-45561
Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Memory corruption while handling IOCTL call from user-space to set latency level.
0
Attacker Value
Unknown
CVE-2024-45560
Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Memory corruption while taking a snapshot with hardware encoder due to unvalidated userspace buffer.
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-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
Attacker Value
Unknown
CVE-2024-45542
Disclosure Date: January 06, 2025 (last updated January 14, 2025)
Memory corruption when IOCTL call is invoked from user-space to write board data to WLAN driver.
0
Attacker Value
Unknown
CVE-2024-45541
Disclosure Date: January 06, 2025 (last updated January 14, 2025)
Memory corruption when IOCTL call is invoked from user-space to read board data.
0