qualcomm fastconnect 7800 firmware vulnerabilities, newest first, page 6

Transient DOS while processing of a registration acceptance OTA due to incorrect ciphering key data IE.

Memory corruption while decoding of OTA messages from T3448 IE.

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 while handling multiple IOCTL calls from userspace to operate DMA operations.

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.

Memory corruption while handling schedule request in Camera Request Manager(CRM) due to invalid link count in the corresponding session.

Memory corruption during concurrent access to server info object due to unprotected critical field.

Memory corruption during concurrent SSR execution due to race condition on the global maps list.

Transient DOS may occur while parsing SSID in action frames.

Memory corruption may occur while processing device IO control call for session control.

Memory corruption when IOCTL call is invoked from user-space to write board data to WLAN driver.

Memory corruption when IOCTL call is invoked from user-space to write board data to WLAN driver.

Memory corruption while IOCTL call is invoked from user-space to read board data.

Memory corruption may occur while initiating two IOCTL calls simultaneously to create processes from two different threads.

Transient DOS may occur while parsing extended IE in beacon.

Transient DOS may occur while parsing EHT operation IE or EHT capability IE.

Transient DOS while connecting STA to AP and initiating ADD TS request from AP to establish TSpec session.

Memory corruption occurs while connecting a STA to an AP and initiating an ADD TS request.

Memory corruption occurs when handling client calls to EnableTestMode through an Escape call.

Memory corruption while processing escape code in API.

Memory corruption while processing multiple IOCTL calls from HLOS to DSP.

Memory corruption can occur when TME processes addresses from TZ and MPSS requests without proper validation.

Cryptographic issue may arise because the access control configuration permits Linux to read key registers in TCSR.

Information disclosure may occur during a video call if a device resets due to a non-conforming RTCP packet that doesn`t adhere to RFC standards.

Cryptographic issue occurs during PIN/password verification using Gatekeeper, where RPMB writes can be dropped on verification failure, potentially leading to a user throttling bypass.

Information disclosure while creating MQ channels.

Memory corruption while accessing MSM channel map and mixer functions.

Memory corruption while invoking IOCTL map buffer request from userspace.

Memory corruption occurs during the copying of read data from the EEPROM because the IO configuration is exposed as shared memory.

Memory corruption while handling file descriptor during listener registration/de-registration.

Cryptographic issues while generating an asymmetric key pair for RKP use cases.

Memory corruption while processing IOCTL calls.

There may be information disclosure during memory re-allocation in TZ Secure OS.

Memory corruption while assigning memory from the source DDR memory(HLOS) to ADSP.

Memory corruption while calling the NPU driver APIs concurrently.

Memory corruption occurs during an Escape call if an invalid Kernel Mode CPU event and sync object handle are passed with the DriverKnownEscape flag reset.