Use After Free in Automotive Telematics
Memory corruption as fence object may still be accessed in timeline destruct after isync fence is released.
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 parsing BTM ML IE when per STA profile is not included.
Transient DOS while processing the CU information from RNR IE.
Transient DOS as modem reset occurs when an unexpected MAC RAR (with invalid PDU length) is seen at UE.
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 while sending the persist buffer command packet from the user-space to the kernel space through the IOCTL call.
Information disclosure while parsing the multiple MBSSID IEs from the beacon.
Transient DOS when transmission of management frame sent by host is not successful and error status is received in the host.
Transient DOS while parsing ESP IE from beacon/probe response frame.
Transient DOS while parsing the MBSSID IE from the beacons when IE length is 0.