Memory corruption while calling the NPU driver APIs concurrently.

Memory corruption may occur in keyboard virtual device due to guest VM interaction.

Memory corruption while reading a type value from a buffer controlled by the Guest Virtual Machine.

Memory corruption while processing input message passed from FE driver.

Memory corruption while reading a value from a buffer controlled by the Guest Virtual Machine.

Memory corruption may occur while processing message from frontend during allocation.

Transient DOS may occur while processing the country IE.

Memory corruption in display driver while detaching a device.

Memory corruption may occur while accessing a variable during extended back to back tests.

Memory corruption may occur while validating ports and channels in Audio driver.

Memory corruption may occur due to improper input validation in clock device.

Information disclosure while deriving keys for a session for any Widevine use case.

Memory corruption during management frame processing due to mismatch in T2LM info element.

Information disclosure while parsing the OCI IE with invalid length.

Memory corruption while reading CPU state data during guest VM suspend.

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

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