CVE-2019-18683: Race Condition
An issue was discovered in drivers/media/platform/vivid in the Linux kernel through 5.3.8. It is exploitable for privilege escalation on some Linux distributions where local users have /dev/video0 access, but only if the driver happens to be loaded. There are multiple race conditions during streaming stopping in this driver (part of the V4L2 subsystem). These issues are caused by wrong mutex locking in vividstopgeneratingvidcap(), vividstopgeneratingvidout(), sdrcapstopstreaming(), and the corresponding kthreads. At least one of these race conditions leads to a use-after-free.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.262-1Fixed in 6.1.176-1Fixed in 6.1.180-1Fixed in 6.12.94-1Fixed in 6.12.101-1Fixed in 7.1.8-1Fixed in 7.1.8-2
Event History
Frequently Asked Questions
What is the severity of CVE-2019-18683?
CVE-2019-18683 has been assigned a severity rating that indicates a potential for privilege escalation under specific conditions.
How do I fix CVE-2019-18683?
To fix CVE-2019-18683, upgrade your Linux kernel to version 5.10.223-1 or later.
Which Linux distributions are affected by CVE-2019-18683?
CVE-2019-18683 affects several Linux distributions where local users have access to /dev/video0 and the vivid driver is loaded.
What kind of vulnerability is CVE-2019-18683?
CVE-2019-18683 is a privilege escalation vulnerability due to race conditions in the Linux kernel's vivid driver.
Is CVE-2019-18683 exploitable remotely?
CVE-2019-18683 is exploitable only by local users, not remotely.