Cryptographic Issues in BT Controller
Cryptographic issue when a controller receives an LMP start encryption command under unexpected conditions.
Cryptographic issue when a controller receives an LMP start encryption command under unexpected conditions.
Memory corruption may occur while validating ports and channels in Audio driver.
Memory corruption while calling the NPU driver APIs concurrently.
Memory corruption during concurrent access to server info object due to incorrect reference count update.
Memory corruption during concurrent buffer access due to modification of the reference count.
Memory corruption during memory assignment to headless peripheral VM due to incorrect error code handling.
Memory corruption during memory mapping into protected VM address space due to incorrect API restrictions.
Memory corruption while triggering commands in the PlayReady Trusted application.
Memory corruption during the FRS UDS generation process.
Memory corruption while processing a data structure, when an iterator is accessed after it has been removed, potential failures occur.
Memory corruption occurs during the copying of read data from the EEPROM because the IO configuration is exposed as shared memory.
Memory corruption occurs while connecting a STA to an AP and initiating an ADD TS request.
Cryptographic issue while processing crypto API calls, missing checks may lead to corrupted key usage or IV reuses.
Memory corruption while submitting blob data to kernel space though IOCTL.
Memory corruption while performing private key encryption in trusted application.
Cryptographic issue while performing RSA PKCS padding decoding.
Memory corruption when the UE receives an RTP packet from the network, during the reassembly of NALUs.
memory corruption while loading a PIL authenticated VM, when authenticated VM image is loaded without maintaining cache coherency.