| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Transient DOS while parsing noninheritance IE of Extension element when length of IE is 2 of beacon frame. |
| Memory corruption when BTFM client sends new messages over Slimbus to ADSP. |
| Transient DOS while parsing MBSSID during new IE generation in beacon/probe frame when IE length check is either missing or improper. |
| Memory corruption in HLOS while checking for the storage type. |
| Memory corruption while verifying the serialized header when the key pairs are generated. |
| Memory corruption while processing buffer initialization, when trusted report for certain report types are generated. |
| Transient DOS can occur when the driver parses the per STA profile IE and tries to access the EXTN element ID without checking the IE length. |
| Memory corruption in Core Services while executing the command for removing a single event listener. |
| Memory corruption while copying the result to the transmission queue which is shared between the virtual machine and the host. |
| 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 |
