Snapdragon W5\+ Gen 1 Wearable Firmware
by Qualcomm
CVEs (298)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2025-21468 | Hig | 0.51 | 7.8 | 0.00 | May 6, 2025 | Memory corruption while reading response from FW, when buffer size is changed by FW while driver is using this size to write null character at the end of buffer. | ||
| CVE-2025-21467 | Hig | 0.51 | 7.8 | 0.00 | May 6, 2025 | Memory corruption while reading the FW response from the shared queue. | ||
| CVE-2025-21453 | Hig | 0.51 | 7.8 | 0.00 | May 6, 2025 | Memory corruption while processing a data structure, when an iterator is accessed after it has been removed, potential failures occur. | ||
| CVE-2024-45576 | Hig | 0.51 | 7.8 | 0.00 | May 6, 2025 | Memory corruption while prociesing command buffer buffer in OPE module. | ||
| CVE-2024-45564 | Hig | 0.51 | 7.8 | 0.00 | May 6, 2025 | Memory corruption during concurrent access to server info object due to incorrect reference count update. | ||
| CVE-2025-21436 | Hig | 0.51 | 7.8 | 0.00 | Apr 7, 2025 | Memory corruption may occur while initiating two IOCTL calls simultaneously to create processes from two different threads. | ||
| CVE-2024-43067 | Hig | 0.51 | 7.8 | 0.00 | Apr 7, 2025 | Memory corruption occurs during the copying of read data from the EEPROM because the IO configuration is exposed as shared memory. | ||
| CVE-2024-43066 | Hig | 0.51 | 7.8 | 0.00 | Apr 7, 2025 | Memory corruption while handling file descriptor during listener registration/de-registration. | ||
| CVE-2025-21424 | Hig | 0.51 | 7.8 | 0.00 | Mar 3, 2025 | Memory corruption while calling the NPU driver APIs concurrently. | ||
| CVE-2024-53024 | Hig | 0.51 | 7.8 | 0.00 | Mar 3, 2025 | Memory corruption in display driver while detaching a device. | ||
| CVE-2024-53023 | Hig | 0.51 | 7.8 | 0.00 | Mar 3, 2025 | Memory corruption may occur while accessing a variable during extended back to back tests. | ||
| CVE-2024-53014 | Hig | 0.51 | 7.8 | 0.00 | Mar 3, 2025 | Memory corruption may occur while validating ports and channels in Audio driver. | ||
| CVE-2024-43057 | Hig | 0.51 | 7.8 | 0.00 | Mar 3, 2025 | Memory corruption while processing command in Glink linux. | ||
| CVE-2024-49843 | Hig | 0.51 | 7.8 | 0.00 | Feb 3, 2025 | Memory corruption while processing IOCTL from user space to handle GPU AHB bus error. | ||
| CVE-2024-49834 | Hig | 0.51 | 7.8 | 0.00 | Feb 3, 2025 | Memory corruption while power-up or power-down sequence of the camera sensor. | ||
| CVE-2024-45584 | Hig | 0.51 | 7.8 | 0.00 | Feb 3, 2025 | Memory corruption can occur when a compat IOCTL call is followed by a normal IOCTL call from userspace. | ||
| CVE-2024-38418 | Hig | 0.51 | 7.8 | 0.00 | Feb 3, 2025 | Memory corruption while parsing the memory map info in IOCTL calls. | ||
| CVE-2024-45553 | Hig | 0.51 | 7.8 | 0.00 | Jan 6, 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. | ||
| CVE-2024-38424 | Hig | 0.51 | 7.8 | 0.00 | Nov 4, 2024 | Memory corruption during GNSS HAL process initialization. | ||
| CVE-2024-38423 | Hig | 0.51 | 7.8 | 0.00 | Nov 4, 2024 | Memory corruption while processing GPU page table switch. |
- risk 0.51cvss 7.8epss 0.00
Memory corruption while reading response from FW, when buffer size is changed by FW while driver is using this size to write null character at the end of buffer.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while reading the FW response from the shared queue.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while processing a data structure, when an iterator is accessed after it has been removed, potential failures occur.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while prociesing command buffer buffer in OPE module.
- risk 0.51cvss 7.8epss 0.00
Memory corruption during concurrent access to server info object due to incorrect reference count update.
- risk 0.51cvss 7.8epss 0.00
Memory corruption may occur while initiating two IOCTL calls simultaneously to create processes from two different threads.
- risk 0.51cvss 7.8epss 0.00
Memory corruption occurs during the copying of read data from the EEPROM because the IO configuration is exposed as shared memory.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while handling file descriptor during listener registration/de-registration.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while calling the NPU driver APIs concurrently.
- risk 0.51cvss 7.8epss 0.00
Memory corruption in display driver while detaching a device.
- risk 0.51cvss 7.8epss 0.00
Memory corruption may occur while accessing a variable during extended back to back tests.
- risk 0.51cvss 7.8epss 0.00
Memory corruption may occur while validating ports and channels in Audio driver.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while processing command in Glink linux.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while processing IOCTL from user space to handle GPU AHB bus error.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while power-up or power-down sequence of the camera sensor.
- risk 0.51cvss 7.8epss 0.00
Memory corruption can occur when a compat IOCTL call is followed by a normal IOCTL call from userspace.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while parsing the memory map info in IOCTL calls.
- risk 0.51cvss 7.8epss 0.00
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.
- risk 0.51cvss 7.8epss 0.00
Memory corruption during GNSS HAL process initialization.
- risk 0.51cvss 7.8epss 0.00
Memory corruption while processing GPU page table switch.
Page 7 of 15