Wsa8815 Firmware vulnerabilities
21 known vulnerabilities in Wsa8815 Firmware from Qualcomm. 21 are rated high or critical, and 2 have been exploited in real attacks. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.0 High severity
Snapdragon: Buffer Over-read
Memory Corruption when multiple threads issue concurrent IOCTL requests to the device control handler due to improper synchronization and race conditions.
- 7.8 High severity
Snapdragon: Use After Free
Memory Corruption when invoking device input/output control operations for mapping and unmapping persistent memory buffers due to improper synchronization.
- 7.5 High severity
Qualcomm Multiple Chipsets Use-After-Free Exploited
Memory corruption while rendering graphics using Adreno GPU drivers in Chrome.
- 7.0 High severity
Snapdragon: Use After Free
Memory corruption while invoking redundant release command to release one buffer from user space as race condition can occur in kernel space between buffer release and buffer access.
- 7.8 High severity
Qualcomm Multiple Chipsets Use-After-Free Exploited
Memory corruption while maintaining memory maps of HLOS memory.
- 7.8 High severity
Snapdragon: Use After Free
In the function call related to CAM_REQ_MGR_RELEASE_BUF there is no check if the buffer is being used. So when a function called cam_mem_get_cpu_buf to get the kernel va to use, another thread can call CAM_REQ_MGR_RELEASE_BUF to unmap the kernel va which cause
- 7.0 High severity
Snapdragon: Time-of-check Time-of-use (TOCTOU) Race Condition
The buffer obtained from kernel APIs such as cam_mem_get_cpu_buf() may be readable/writable in userspace after kernel accesses it. In other words, user mode may race and modify the packet header (e.g. header.count), causing checks (e.g. size checks) in kernel
- 7.8 High severity
Snapdragon: Access of Resource Using Incompatible Type
The cam_get_device_priv function does not check the type of handle being returned (device/session/link). This would lead to invalid type usage if a wrong handle is passed to it.
- 7.8 High severity
Snapdragon Auto, Snapdragon Compute…: Buffer Copy without Checking Size of Input
Memory corruption in camera due to buffer copy without checking size of input in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Wearables
- 7.8 High severity
Snapdragon Auto, Snapdragon Compute…: Improper Validation of Array Index
Memory corruption in camera due to improper validation of array index in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables
- 7.5 High severity
Snapdragon Consumer IOT, Snapdragon Industrial…: Loop with Unreachable Exit Condition
Denial of service in modem due to infinite loop while parsing IGMPv2 packet from server in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music
- 9.8 Critical severity
Snapdragon Consumer IOT, Snapdragon Industrial…: Improper Validation of Specified Quantity in Input
Memory Corruption in modem due to improper length check while copying into memory in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music
- 9.8 Critical severity
Snapdragon Auto, Snapdragon Consumer IOT…: Integer Overflow or Wraparound
Memory corruption in bluetooth due to integer overflow while processing HFP-UNIT profile in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Voice & Music
- 7.8 High severity
Snapdragon Compute, Snapdragon Connectivity…: Use After Free
Memory corruption in synx driver due to use-after-free condition in the synx driver due to accessing object handles without acquiring lock in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile
- 7.0 High severity
Snapdragon Compute, Snapdragon Connectivity…: Time-of-check Time-of-use (TOCTOU) Race Condition
memory corruption in Kernel due to race condition while getting mapping reference in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile
- 7.0 High severity
Snapdragon Compute, Snapdragon Connectivity…: Time-of-check Time-of-use (TOCTOU) Race Condition
Memory corruption or temporary denial of service due to improper handling of concurrent hypervisor operations to attach or detach IRQs from virtual interrupt sources in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile
- 9.8 Critical severity
Snapdragon Connectivity, Snapdragon Mobile: Out-of-bounds Write
Memory corruption in Bluetooth HOST due to stack-based buffer overflow when when extracting data using command length parameter in Snapdragon Connectivity, Snapdragon Mobile
- 7.8 High severity
Snapdragon Auto, Snapdragon Compute…: Missing Release of Memory after Effective Lifetime
Potential memory leak in modem during the processing of NSA RRC Reconfiguration with invalid Radio Bearer Config in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile
- 9.8 Critical severity
Snapdragon Auto, Snapdragon Consumer IOT…: Integer Overflow or Wraparound
Memory corruption in bluetooth host due to integer overflow while processing BT HFP-UNIT profile in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music
- 7.8 High severity
Snapdragon Compute, Snapdragon Connectivity…: Use After Free
Memory corruption in audio due to use after free while managing buffers from internal cache in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile
- 7.8 High severity
Snapdragon Auto, Snapdragon Compute…: Improper Validation of Specified Quantity in Input
Buffer overflow can occur due to improper validation of NDP application information length in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon V