It's an out-of-bounds write, caused by injecting UVC_VS_UNDEFINED frames into the video file, as they weren't size-handled correctly. Which means, unfortunatel

It's an out-of-bounds write, caused by injecting UVC_VS_UNDEFINED frames into the video file, as they weren't size-handled correctly. Which means, unfortunately, that playing a video file with that particular driver is all that would be needed. The constructed video file would need a second exploit to jump out of the virtual memory of the driver and into the kernel, but that has happened before [1]. It's a high risk. Or it could just be used to crash every device that sees the video in a DoS attack. However, the devices that use those drivers tend not to be end-user devices (webcams, smart TVs, TV tuners, recorders, etc.) They would be used as an entrypoint, before moving laterally into a network. So, standard IoT type breach. [0] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=faff5bbb2762c44ec7426037b3000e77a11d6773 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux... [1] https://github.com/0xdevil/CVE-2021-42008 https://github.com/0xdevil/CVE-2021-42008