Vulnerabilidades

Memory corruption while power-up or power-down sequence of the camera sensor.

Memory corruption can occur in the camera when an invalid CID is used.

Memory corruption in Camera due to unusually high number of nodes passed to AXI port.

Memory corruption can occur when a compat IOCTL call is followed by a normal IOCTL call from userspace.

Memory corruption while validating number of devices in Camera kernel .

Memory corruption may occour occur when stopping the WLAN interface after processing a WMI command from the interface.

Memory corruption while parsing the ML IE due to invalid frame content.

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 can occur when process-specific maps are added to the global list. If a map is removed from the global list while another thread is using it for a process-specific task, issues may arise.

Memory corruption while processing API calls to NPU with invalid input.

Memory corruption when invalid input is passed to invoke GPU Headroom API call.

Transient DOS while parsing the ML IE when a beacon with common info length of the ML IE greater than the ML IE inside which this element is present.

Memory corruption when allocating and accessing an entry in an SMEM partition continuously.

Memory corruption during GNSS HAL process initialization.

Memory corruption while processing GPU commands.

Memory corruption while handling session errors from firmware.

Cryptographic issue when a controller receives an LMP start encryption command under unexpected conditions.

Transient DOS while processing the CU information from RNR IE.

Transient DOS while parsing BTM ML IE when per STA profile is not included.

Transient DOS while parsing fragments of MBSSID IE from beacon frame.