Vulnerabilidades

Memory corruption may occur while attaching VM when the HLOS retains access to VM.

Memory corruption while processing escape code, when DisplayId is passed with large unsigned value.

Memory corruption while processing image encoding, when configuration is NULL in IOCTL parameter.

Memory corruption while processing image encoding, when input buffer length is 0 in IOCTL call.

Memory corruption while processing an IOCTL request, when buffer significantly exceeds the command argument limit.

Memory corruption during the FRS UDS generation process.

Memory corruption while triggering commands in the PlayReady Trusted application.

Memory corruption during memory mapping into protected VM address space due to incorrect API restrictions.

Memory corruption during memory assignment to headless peripheral VM due to incorrect error code handling.

Memory corruption while reading secure file.

Transient DOS may occur while parsing SSID in action frames.

Memory corruption may occur while processing device IO control call for session control.

Memory corruption when IOCTL call is invoked from user-space to write board data to WLAN driver.

Memory corruption when IOCTL call is invoked from user-space to write board data to WLAN driver.

Memory corruption while IOCTL call is invoked from user-space to read board data.

Memory corruption occurs when handling client calls to EnableTestMode through an Escape call.

Memory corruption while processing escape code in API.

Memory corruption can occur when TME processes addresses from TZ and MPSS requests without proper validation.

Cryptographic issue occurs during PIN/password verification using Gatekeeper, where RPMB writes can be dropped on verification failure, potentially leading to a user throttling bypass.

Information disclosure while creating MQ channels.

Cryptographic issues while generating an asymmetric key pair for RKP use cases.

There may be information disclosure during memory re-allocation in TZ Secure OS.

Memory corruption while assigning memory from the source DDR memory(HLOS) to ADSP.

Memory corruption occurs during an Escape call if an invalid Kernel Mode CPU event and sync object handle are passed with the DriverKnownEscape flag reset.

Memory corruption while doing Escape call when user provides valid kernel address in the place of valid user buffer address.