Integer Overflow or Wraparound in HLOS
Memory corruption in HLOS while checking for the storage type.
Memory corruption in HLOS while checking for the storage type.
Memory corruption while processing finish_sign command to pass a rsp buffer.
Memory corruption while processing buffer initialization, when trusted report for certain report types are generated.
Memory corruption when BTFM client sends new messages over Slimbus to ADSP.
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.
Transient DOS may occur while processing the country IE.
Memory corruption whhile handling the subsystem failure memory during the parsing of video packets received from the video firmware.
Memory corruption when multiple listeners are being registered with the same file descriptor.
Transient DOS while parsing the received TID-to-link mapping element of beacon/probe response frame.
Information disclosure when the ADSP payload size received in HLOS in response to Audio Stream Manager matrix session is less than this expected size.
Transient DOS may occur when processing vendor-specific information elements while parsing a WLAN frame for BTM requests.
Transient DOS when importing a PKCS#8-encoded RSA private key with a zero-sized modulus.
Transient DOS while parsing probe response and assoc response frame.
Memory corruption while processing data packets in diag received from Unix clients.
Memory corruption when the payload received from firmware is not as per the expected protocol size.
Memory corruption when IOMMU unmap of a GPU buffer fails in Linux.
Memory corruption while copying the result to the transmission queue which is shared between the virtual machine and the host.
Transient DOS can occur when GVM sends a specific message type to the Vdev-FastRPC backend.
Memory corruption can occur if an already verified IFS2 image is overwritten, bypassing boot verification. This allows unauthorized programs to be injected into security-sensitive images, enabling the booting of a tampered IFS2 system image.