qualcomm fastconnect 6900 firmware vulnerabilities, newest first, page 5

Memory corruption while processing video packets received from video firmware.

Memory corruption while processing a private escape command in an event trigger.

Transient DOS while processing received beacon frame.

Cryptographic issue occurs due to use of insecure connection method while downloading.

Transient DOS may occur while processing malformed length field in SSID IEs.

Transient DOS may occur when processing vendor-specific information elements while parsing a WLAN frame for BTM requests.

Transient DOS when importing a PKCS#8-encoded RSA private key with a zero-sized modulus.

Memory corruption while retrieving the CBOR data from TA.

Information disclosure while decoding this RTP packet Payload when UE receives the RTP packet from the network.

Cryptographic issue while processing crypto API calls, missing checks may lead to corrupted key usage or IV reuses.

Memory corruption while operating the mailbox in Automotive.

Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands.

memory corruption while processing IOCTL commands, when the buffer in write loopback mode is accessed after being freed.

Memory corruption during dynamic process creation call when client is only passing address and length of shell binary.

Memory corruption while processing INIT and multimode invoke IOCTL calls on FastRPC.

Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands.

Transient DOS while processing the EHT operation IE in the received beacon frame.

Information disclosure when an invalid RTCP packet is received during a VoLTE/VoWiFi IMS call.

Information disclosure may occur while processing goodbye RTCP packet from network.

Information disclosure may occur while decoding the RTP packet with invalid header extension from network.

Information disclosure may occur while decoding the RTP packet with improper header length for number of contributing sources.

Memory corruption may occur while processing the OIS packet parser.

Memory corruption while processing I2C settings in Camera driver.

Memory corruption while processing IOCTL command to handle buffers associated with a session.

Memory corruption may occur while processing voice call registration with user.

Memory corruption may occur while attaching VM when the HLOS retains access to VM.

Memory corruption while processing escape code, when DisplayId is passed with large unsigned value.

Memory corruption while processing image encoding, when configuration is NULL in IOCTL parameter.

Memory corruption while processing image encoding, when input buffer length is 0 in IOCTL call.

Memory corruption while reading response from FW, when buffer size is changed by FW while driver is using this size to write null character at the end of buffer.

Memory corruption while reading the FW response from the shared queue.

Memory corruption while processing an IOCTL request, when buffer significantly exceeds the command argument limit.

Transient DOS while parsing per STA profile in ML IE.

Memory corruption while processing a data structure, when an iterator is accessed after it has been removed, potential failures occur.

Memory corruption during the FRS UDS generation process.

Memory corruption while triggering commands in the PlayReady Trusted application.

Memory corruption during memory mapping into protected VM address space due to incorrect API restrictions.

Memory corruption during memory assignment to headless peripheral VM due to incorrect error code handling.

Memory corruption while reading secure file.

Memory corruption can occur during context user dumps due to inadequate checks on buffer length.

Memory corruption may occur when invoking IOCTL calls from userspace to the camera kernel driver to dump request information, due to a missing memory requirement check.

Memory corruption while acquire and update IOCTLs during IFE output resource ID validation.

Memory corruption while invoking IOCTL calls from userspace to camera kernel driver to dump request information.

Memory corruption while prociesing command buffer buffer in OPE module.

Memory corruption Camera kernel when large number of devices are attached through userspace.

Memory corruption may occur during IO configuration processing when the IO port count is invalid.

Memory corruption due to improper bounds check while command handling in camera-kernel driver.

Memory corruption while encoding JPEG format.

Memory corruption during concurrent buffer access due to modification of the reference count.

Memory corruption during concurrent access to server info object due to incorrect reference count update.