Improper Restriction of Operations within the Bounds of a Memory Buffer in HLOS
Memory corruption when invalid length is provided from HLOS for FRS/UDS request/response buffers.
Memory corruption when invalid length is provided from HLOS for FRS/UDS request/response buffers.
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.
Transient DOS while parsing MBSSID during new IE generation in beacon/probe frame when IE length check is either missing or improper.
Memory corruption when two threads try to map and unmap a single node simultaneously.
Information disclosure while parsing the BSS parameter change count or MLD capabilities fields of the ML IE.
Transient DOS while processing received beacon frame.
Information disclosure while deriving keys for a session for any Widevine use case.
Transient DOS during hypervisor virtual I/O operation in a virtual machine.
Memory corruption while processing IOCTL call for getting group info.
Memory corruption during management frame processing due to mismatch in T2LM info element.
Memory corruption when preparing a shared memory notification for a memparcel in Resource Manager.
Memory corruption while processing manipulated payload in video firmware.
Transient DOS when importing a PKCS#8-encoded RSA private key with a zero-sized modulus.
Memory corruption when BTFM client sends new messages over Slimbus to ADSP.
Transient DOS while processing TIM IE from beacon frame as there is no check for IE length.
Transient DOS while parsing the multi-link element Control field when common information length check is missing before updating the location.
Transient DOS while parsing the received TID-to-link mapping element of beacon/probe response frame.
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.