Buffer Copy Without Checking Size of Input in Trusted Execution Environment
Memory corruption while copying a keyblob`s material when the key material`s size is not accurately checked.
Memory corruption while copying a keyblob`s material when the key material`s size is not accurately checked.
Memory Corruption in Core due to secure memory access by user while loading modem image.
Transient DOS while processing TIM IE from beacon frame as there is no check for IE length.
Memory Corruption in WLAN HOST while parsing QMI response message from firmware.
Memory Corruption in Audio while allocating the ion buffer during the music playback.
Transient DOS may occur when processing vendor-specific information elements while parsing a WLAN frame for BTM requests.
Memory corruption while processing manipulated payload in video firmware.
Memory corruption while processing data packets in diag received from Unix clients.
Memory corruption while playing audio file having large-sized input buffer.
Memory Corruption in Modem due to double free while parsing the PKCS15 sim files.
Memory corruption when BTFM client sends new messages over Slimbus to ADSP.
Improper Access to the VM resource manager can lead to Memory Corruption.
Memory corruption while processing buffer initialization, when trusted report for certain report types are generated.
Arbitrary memory overwrite when VM gets compromised in TX write leading to Memory Corruption.
Memory corruption when the payload received from firmware is not as per the expected protocol size.
Memory corruption while invoking HGSL IOCTL context create.
Memory corruption while processing Listen Sound Model client payload buffer when there is a request for Listen Sound session get parameter from ST HAL.
Memory corruption when two threads try to map and unmap a single node simultaneously.
Transient DOS while parsing IPv6 extension header when WLAN firmware receives an IPv6 packet that contains `IPPROTO_NONE` as the next header.
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.