Kernel crash via unchecked TW5864 video buffer
Published May 27, 2020 · Updated Aug 5, 2024
NULL pointer dereference in the Linux kernel before 5.2 allows local users with high privileges to crash the system through the TW5864 video driver. tw5864_handle_frame() converts vb to a V4L2 buffer before checking whether vb is NULL after frame capture is disabled. Exploitation requires local high privileges and an active TW5864 capture path; the documented consequence is a kernel crash and service interruption.
Summary
What happened
NULL pointer dereference in the Linux kernel before 5.2 allows local users with high privileges to crash the system through the TW5864 video driver. tw5864_handle_frame() converts vb to a V4L2 buffer before checking whether vb is NULL after frame capture is disabled. Exploitation requires local high privileges and an active TW5864 capture path; the documented consequence is a kernel crash and service interruption.
The record
- CVE
- CVE-2019-20806
- Published
- May 27, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 27, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo