Vulnerabilidades

While processing the authentication message in UE, improper authentication may lead to information disclosure.

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.

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 when invalid input is passed to invoke GPU Headroom API call.

Memory corruption when allocating and accessing an entry in an SMEM partition continuously.

Memory corruption during GNSS HAL process initialization.

Memory corruption while processing voice packet with arbitrary data received from ADSP.

Memory corruption while invoking IOCTL calls from the use-space for HGSL memory node.

Memory corruption while maintaining memory maps of HLOS memory.

Memory corruption while processing user packets to generate page faults.

Transient DOS while parsing noninheritance IE of Extension element when length of IE is 2 of beacon frame.

Memory corruption when a compat IOCTL call is followed by another IOCTL call from userspace to a driver.

Memory corruption while processing IOCTL call for getting group info.

Memory corruption when two threads try to map and unmap a single node simultaneously.

Memory corruption when user provides data for FM HCI command control operations.

Transient DOS while processing TIM IE from beacon frame as there is no check for 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 BTFM client sends new messages over Slimbus to ADSP.

Transient DOS while handling PS event when Program Service name length offset value is set to 255.

Memory corruption when Alternative Frequency offset value is set to 255.

memory corruption when an invalid firehose patch command is invoked.

Memory corruption can occur if VBOs hold outdated or invalid GPU SMMU mappings, especially when the binding and reclaiming of memory buffers are performed at the same time.

Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released.

Memory corruption while creating a fence to wait on timeline events, and simultaneously signal timeline events.