Buffer Over-read in WLAN Host
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 probe response and assoc response frame when received frame length is less than max size of timestamp.
Memory corruption while creating a fence to wait on timeline events, and simultaneously signal timeline events.
Memory corruption while allocating memory in HGSL driver.
Memory corruption while processing IOCTL call to set metainfo.
Transient DOS while processing TID-to-link mapping IE elements.
Transient DOS while parsing the received TID-to-link mapping action frame.
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.
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 when the user application modifies the same shared memory asynchronously when kernel is accessing it.
Transient DOS while parsing fragments of MBSSID IE from beacon frame.
Transient DOS while processing the CU information from RNR IE.
Memory corruption while processing GPU page table switch.
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 handling session errors from firmware.
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 during the network scan request.