Buffer Copy Without Checking Size of Input in WLAN Host
Transient DOS may occur while processing the country IE.
Transient DOS may occur while processing the country IE.
Memory corruption when two threads try to map and unmap a single node simultaneously.
Transient DOS while parsing the multi-link element Control field when common information length check is missing before updating the location.
Transient DOS while processing TIM IE from beacon frame as there is no check for IE length.
Transient DOS when importing a PKCS#8-encoded RSA private key with a zero-sized modulus.
Memory corruption when preparing a shared memory notification for a memparcel in Resource Manager.
Transient DOS while parsing MBSSID during new IE generation in beacon/probe frame when IE length check is either missing or improper.
Transient DOS while parsing the received TID-to-link mapping element of beacon/probe response frame.
Memory corruption when BTFM client sends new messages over Slimbus to ADSP.
Transient DOS may occur when processing vendor-specific information elements while parsing a WLAN frame for BTM requests.
Transient DOS while parsing per STA profile in ML IE.
Memory corruption while processing manipulated payload in video firmware.
Memory corruption whhile handling the subsystem failure memory during the parsing of video packets received from the video firmware.
Memory corruption when invalid length is provided from HLOS for FRS/UDS request/response buffers.
Memory corruption while copying the result to the transmission queue which is shared between the virtual machine and the host.
Transient DOS can occur when GVM sends a specific message type to the Vdev-FastRPC backend.
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.
Uncontrolled resource consumption when a driver, an application or a SMMU client tries to access the global registers through SMMU.
Information disclosure while parsing the OCI IE with invalid length.
Memory corruption can occur when a compat IOCTL call is followed by a normal IOCTL call from userspace.