Key Management Errors in HLOS
Cryptographic issue in HLOS as derived keys used to encrypt/decrypt information is present on stack after use.
Cryptographic issue in HLOS as derived keys used to encrypt/decrypt information is present on stack after use.
Memory Corruption in Core due to incorrect type conversion or cast in secure_io_read/write function in TEE.
Memory Corruption in GPS HLOS Driver when injectFdclData receives data with invalid data length.
Memory corruption in WLAN while running doDriverCmd for an unspecific command.
Information disclosure in Bluetooth when an GATT packet is received due to improper input validation.
Transient DOS in Modem while processing invalid System Information Block 1.
Memory corruption in RIL due to Integer Overflow while triggering qcril_uim_request_apdu request.
Memory Corruption due to improper validation of array index in Linux while updating adn record.
Memory corruption in WLAN HAL while processing WMI-UTF command or FTM TLV1 command.
Memory corruption in Trusted Execution Environment while calling service API with invalid address.
Cryptographic issue in HLOS due to improper authentication while performing key velocity checks using more than one key.
Memory corruption in Bluetooth HOST while processing the AVRC_PDU_GET_PLAYER_APP_VALUE_TEXT AVRCP response.
Transient DOS due to improper authentication in modem while receiving plain TLB OTA request message from network.
Transient DOS due to buffer over-read in WLAN while sending a packet to device.
Transient DOS due to untrusted Pointer Dereference in core while sending USB QMI request.
Memory corruption due to integer overflow or wraparound in WLAN while sending WMI cmd from host to target.
Memory corruption in WLAN due to incorrect type cast while sending WMI_SCAN_SCH_PRIO_TBL_CMDID message.
Memory corruption in WLAN due to integer overflow to buffer overflow in WLAN during initialization phase.
Memory corruption due to improper access control in kernel while processing a mapping request from root process.
Transient DOS due to reachable assertion in WLAN while processing PEER ID populated by TQM.