Wcn3950 Firmware vulnerabilities
14 known vulnerabilities in Wcn3950 Firmware from Qualcomm. 14 are rated high or critical, and 3 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.1 High severity
Snapdragon: Reusing a Nonce, Key Pair in Encryption
Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.
- 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.
- 8.6 High severity
Qualcomm Multiple Chipsets Incorrect Authorization Exploited
Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands.
- 7.5 High severity
Qualcomm Multiple Chipsets Use-After-Free Exploited
Memory corruption while rendering graphics using Adreno GPU drivers in Chrome.
- 7.8 High severity
Snapdragon: Out-of-bounds Write
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.
- 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.8 High severity
Snapdragon Auto, Snapdragon Compute…: Integer Overflow or Wraparound
Possible integer overflow and memory corruption due to improper validation of buffer size sent to write to console when computing the payload size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Sn
- 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
- 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