| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Memory corruption when BTFM client sends new messages over Slimbus to ADSP. |
| Transient DOS while parsing noninheritance IE of Extension element when length of IE is 2 of beacon frame. |
| Transient DOS while processing TIM IE from beacon frame as there is no check for IE length. |
| Transient DOS while parsing the multi-link element Control field when common information length check is missing before updating the location. |
| Memory corruption when multiple listeners are being registered with the same file descriptor. |
| Memory corruption while processing the event ring, the context read pointer is untrusted to HLOS and when it is passed with arbitrary values, may point to address in the middle of ring element. |
| Memory corruption when AP includes TID to link mapping IE in the beacons and STA is parsing the beacon TID to link mapping IE. |
| Memory corruption while copying the result to the transmission queue which is shared between the virtual machine and the host. |
| Memory corruption while invoking IOCTL calls from the use-space for HGSL memory node. |
| Memory corruption in Core when updating rollback version for TA and OTA feature is enabled. |
| Cryptographic issue in Automotive while unwrapping the key secs2d and verifying with RPMB data. |
| Memory corruption in HLOS while running playready use-case. |
| Memory corruption in Automotive Multimedia due to improper access control in HAB. |
| Information disclosure due to buffer over read in kernel in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile |
| Memory corruption due to untrusted pointer dereference in kernel in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile |
| Memory corruption due to double free issue in kernel in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile |
| Memory corruption in automotive multimedia due to use of out-of-range pointer offset while parsing command request packet with a very large type value. in Snapdragon Auto |
| Memory corruption may occur during IO configuration processing when the IO port count is invalid. |
| Possible memory corruption in kernel while performing memory access due to hypervisor not correctly invalidated the processor translation caches in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile |
| Memory corruption due to stack-based buffer overflow in Core |
