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 while generating test pattern due to negative indexing of display ID.

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.

Memory corruption while handling IOCTL call from user-space to set latency level.

Memory corruption while taking a snapshot with hardware encoder due to unvalidated userspace buffer.

Memory corruption while configuring a Hypervisor based input virtual device.

Memory corruption while parsing the memory map info in IOCTL calls.

Information disclosure while processing IO control commands.

Information disclosure during audio playback.

Information disclosure while processing information on firmware image during core initialization.

Memory corruption while processing frame packets.

Memory corruption while invoking IOCTL calls from user-space to kernel-space to handle session errors.

Memory corruption while registering a buffer from user-space to kernel-space using IOCTL calls.

Transient DOS when registration accept OTA is received with incorrect ciphering key data IE in modem.

Transient DOS can occur when GVM sends a specific message type to the Vdev-FastRPC backend.

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 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.

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 occurs when invoking any IOCTL-calling application that executes all MCDM driver IOCTL calls.

Memory corruption while processing FIPS encryption or decryption validation functionality IOCTL call.