6419 matches found
CVE-2025-21437 Use After Free in Automotive Linux OS
Memory corruption while processing memory map or unmap IOCTL operations simultaneously...
CVE-2025-21437 Use After Free in Automotive Linux OS
Memory corruption while processing memory map or unmap IOCTL operations simultaneously...
CVE-2025-21437
The connected sources describe CVE-2025-21437 as a race condition in Qualcomm chipset memory management: when processing memory map and unmap IOCTLs concurrently, a use-after-free causes memory corruption. Root cause is a missing synchronization between hfastrpc mem map and mem unmap operations, ...
CVE-2025-21436 Use After Free in DSP Service
Memory corruption may occur while initiating two IOCTL calls simultaneously to create processes from two different threads...
CVE-2025-21436
CVE-2025-21436 describes a memory corruption vulnerability in Qualcomm/SoC kernel code triggered when two IOCTL calls are initiated concurrently from two different threads to create processes. The issue is characterized by local attack vector with low privileges required and no user interaction, ...
CVE-2025-21436 Use After Free in DSP Service
Memory corruption may occur while initiating two IOCTL calls simultaneously to create processes from two different threads...
CVE-2024-49848 Use After Free in DSP Service
Memory corruption while processing multiple IOCTL calls from HLOS to DSP...
CVE-2024-49848 Use After Free in DSP Service
Memory corruption while processing multiple IOCTL calls from HLOS to DSP...
CVE-2024-49848
CVE-2024-49848 concerns memory corruption in Qualcomm ADSPRPC FP/DSP interaction (the adsprpc kernel driver) via fastrpc_mmap structures. The provided sources describe a use-after-free vulnerability in FASTRPC_ATTR_KEEP_MAP handling that can allow a freed fastrpc_mmap object to be referenced by a...
CVE-2024-45544
CVE-2024-45544 is a memory corruption issue in Qualcomm hardware triggered by IOCTL processing for adding a route entry. Documented as affecting Qualcomm kernel components; vector is Local with Low privileges required, no user interaction. Impact is Confidentiality: Low, Integrity: High, Availabi...
CVE-2024-45544 Use After Free in Data Network Stack & Connectivity
Memory corruption while processing IOCTL calls to add route entry in the HW...
CVE-2024-45544 Use After Free in Data Network Stack & Connectivity
Memory corruption while processing IOCTL calls to add route entry in the HW...
CVE-2024-45540 Use After Free in HLOS
Memory corruption while invoking IOCTL map buffer request from userspace...
CVE-2024-45540
CVE-2024-45540 is a memory corruption vulnerability in Qualcomm chipset components related to processing user-space IOCTL mapped buffer requests. Multiple sources (NVD, Red Hat, CVE List, CNNVD, CIRCL) report the issue as memory corruption tied to an IOCTL map-buffer path, with the Pixel Watch bu...
CVE-2024-45540 Use After Free in HLOS
Memory corruption while invoking IOCTL map buffer request from userspace...
CVE-2024-43058
CVE-2024-43058 corresponds to a memory corruption issue occurring when Qualcomm chipset IOCTL calls are processed. The vulnerability affects Qualcomm chipsets and is attributed to a faulty IOCTL handling path, leading to potential impact on confidentiality, integrity, and availability as indicate...
CVE-2024-43058 Incorrect Type Conversion or Cast in Multimedia Frameworks
Memory corruption while processing IOCTL calls...
CVE-2024-43058 Incorrect Type Conversion or Cast in Multimedia Frameworks
Memory corruption while processing IOCTL calls...
PT-2025-15209 · Qualcomm · Snapdragon +22
Name of the Vulnerable Software and Affected Versions: The product name cannot be determined. Description: Memory corruption may occur while initiating two IOCTL calls simultaneously to create processes from two different threads. Recommendations: At the moment, there is no information about a...
PT-2025-15188 · Qualcomm · Snapdragon +6
Name of the Vulnerable Software and Affected Versions: The product name cannot be determined. Description: Memory corruption occurs while processing IOCTL calls. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability...