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 vivid_stop_generating_vid_cap(), vivid_stop_generating_vid_out(), sdr_cap_stop_streaming(), and the corresponding kthreads. At least one of these race conditions leads to a use-after-free.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
Configuration 5 (hide)
|
Configuration 6 (hide)
AND |
|
Configuration 7 (hide)
AND |
|
Configuration 8 (hide)
AND |
|
Configuration 9 (hide)
AND |
|
Configuration 10 (hide)
AND |
|
Configuration 11 (hide)
|
Information
Published : 2019-11-04 08:15
Updated : 2022-04-18 08:46
NVD link : CVE-2019-18683
Mitre link : CVE-2019-18683
JSON object : View
CWE
Products Affected
netapp
- cloud_backup
- a400_firmware
- h610s_firmware
- active_iq_unified_manager
- steelstore_cloud_integrated_storage
- h610s
- a400
- data_availability_services
- e-series_santricity_os_controller
- 8700
- element_software
- solidfire
- 8700_firmware
- 8300_firmware
- 8300
- a700s
- a700s_firmware
- hci_management_node
canonical
- ubuntu_linux
linux
- linux_kernel
debian
- debian_linux
broadcom
- fabric_operating_system
opensuse
- leap