Memory corruption while processing MBSSID beacon containing several subelement IE.
Memory corruption while parsing beacon/probe response frame when AP sends more supported links in MLIE.
Memory corruption while redirecting log file to any file location with any file name.
Memory corruption while parsing the ML IE due to invalid frame content.
Memory corruption during management frame processing due to mismatch in T2LM info element.
Information disclosure in Modem while processing SIB5.
Information Disclosure while parsing beacon frame in STA.
Cryptographic issue when a controller receives an LMP start encryption command under unexpected conditions.
Memory corruption while decoding of OTA messages from T3448 IE.
Cryptographic issue occurs due to use of insecure connection method while downloading.
Memory corruption in core services when Diag handler receives a command to configure event listeners.
Memory corruption while processing TPC target power table in FTM TPC.
Memory corruption while loading a VM from a signed VM image that is not coherent in the processor cache.
Memory corruption while performing finish HMAC operation when context is freed by keymaster.
Memory corruption while processing IOCTL call to set metainfo.
Memory corruption while allocating memory in HGSL driver.
Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released.
Memory corruption while Configuring the SMR/S2CR register in Bypass mode.
Memory corruption in Core when updating rollback version for TA and OTA feature is enabled.
Memory corruption while copying the sound model data from user to kernel buffer during sound model register.
Memory corruption while processing key blob passed by the user.
Memory corruption when an invoke call and a TEE call are bound for the same trusted application.
Memory corruption when keymaster operation imports a shared key.
Memory corruption during session sign renewal request calls in HLOS.
Memory corruption while invoking IOCTL calls from the use-space for HGSL memory node.
Memory corruption while processing voice packet with arbitrary data received from ADSP.
Memory corruption during GNSS HAL process initialization.
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.
Memory corruption may occour occur when stopping the WLAN interface after processing a WMI command from the interface.
Memory corruption during memory mapping into protected VM address space due to incorrect API restrictions.