Permissions, Privileges, and Access Controls in Video Analytics and Processing
Information disclosure may occur due to improper permission and access controls to Video Analytics engine.
Information disclosure may occur due to improper permission and access controls to Video Analytics engine.
Memory corruption may occur while validating ports and channels in Audio driver.
Memory corruption may occur while accessing a variable during extended back to back tests.
Memory corruption in display driver while detaching a device.
Memory corruption may occur while processing message from frontend during allocation.
Memory corruption while processing input message passed from FE driver.
Memory corruption while calling the NPU driver APIs concurrently.
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 while parsing the ML IE due to invalid frame content.
Memory corruption during concurrent access to server info object due to incorrect reference count update.
Memory corruption while sound model registration for voice activation with audio kernel driver.
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 while processing a message, when the buffer is controlled by a Guest VM, the value can be changed continuously.
Memory corruption while processing an IOCTL request, when buffer significantly exceeds the command argument limit.
Memory corruption while reading the FW response from the shared queue.
Memory corruption while reading response from FW, when buffer size is changed by FW while driver is using this size to write null character at the end of buffer.
Memory corruption occurs during the copying of read data from the EEPROM because the IO configuration is exposed as shared memory.