Vulnerabilidades

Memory corruption while sending the persist buffer command packet from the user-space to the kernel space through the IOCTL call.

Memory corruption is possible when an attempt is made from userspace or console to write some haptics effects pattern to the haptics debugfs file.

Memory corruption when invalid length is provided from HLOS for FRS/UDS request/response buffers.

Memory corruption while processing IOCTL call for getting group info.

Memory corruption while processing concurrent IOCTL calls.

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

Transient DOS while parsing the multi-link element Control field when common information length check is missing before updating the location.

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.

Transient DOS while parsing the received TID-to-link mapping element of beacon/probe response frame.

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 while calculating total metadata size when a very high reserved size is requested by gralloc clients.

memory corruption when an invalid firehose patch command is invoked.

Memory corruption while releasing shared resources in MinkSocket listener thread.

Transient DOS when processing the non-transmitted BSSID profile sub-elements present within the MBSSID Information Element (IE) of a beacon frame that is received from over-the-air (OTA).

Cryptographic issue while parsing RSA keys in COBR format.

Information disclosure while decoding Tracking Area Update Accept or Attach Accept message received from network.

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 can occur when arbitrary user-space app gains kernel level privilege to modify DDR memory by corrupting the GPU page table.

Transient DOS while parsing probe response and assoc response frame when received frame length is less than max size of timestamp.

Transient DOS while parsing the BSS parameter change count or MLD capabilities fields of the ML IE.