Vulnerability in drm/vc4: txp: Don't set TXP_VSTART_AT_EOF
Summary
GSD-2022-1003809: drm/vc4: txp: Don't set TXP_VSTART_AT_EOF. Affects Kernel versions >= 008095e065a85a13ffb41b9c98149456267c30b8, < 8a60b54e41c9f745059c057ce3d726f742c0936c. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The drm/vc4 package is a component of the Linux Kernel that provides support for the VC4 graphics driver on Broadcom VideoCore IV GPUs. This driver is responsible for managing the display and rendering capabilities of these GPUs. The vulnerability identified in this package relates to the handling of the TXP_VSTART_AT_EOF flag. This flag controls the vertical synchronization of the display, and the vulnerability arises from improper handling of this flag.
Vulnerability Detail
The vulnerability in drm/vc4 arises from the improper setting of the TXP_VSTART_AT_EOF flag. This flag controls the vertical synchronization of the display, and when set incorrectly, it can lead to various issues. An attacker could potentially exploit this vulnerability to manipulate the display synchronization, resulting in visual artifacts, screen tearing, or even denial of service. The vulnerability was introduced in version v4.19 of the Linux Kernel and has been fixed in version v5.4.198.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
No workaround has been provided for this vulnerability.
Conclusion
The vulnerability in drm/vc4 related to the improper setting of the TXP_VSTART_AT_EOF flag can lead to visual artifacts, screen tearing, or denial of service. It is recommended to update the Linux Kernel to version v5.4.198 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can result in visual artifacts, screen tearing, or denial of service.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it for any open-source vulnerabilities, including this one.
At this time, there is no known exploit for this vulnerability. However, it is still recommended to apply the necessary updates to mitigate any potential risks.
No, this vulnerability requires local access to the affected system in order to exploit it.
This vulnerability affects systems running the Linux Kernel version v4.19 to v5.4.197. Systems running older or newer versions of the kernel are not affected.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
