Cleanup connector on bridge detach vulnerability in Kernel
Summary
GSD-2021-1000302: drm: bridge/panel: Cleanup connector on bridge detach. Affects Kernel versions >= 13dfc0540a575b47b2d640b093ac16e9e09474f6, < 98d7d76a74e48ec3ddf2e23950adff7edcab9327. 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 Kernel is a crucial component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential functionalities and services to enable the proper functioning of the system. The vulnerability in question affects the bridge/panel module of the Kernel, specifically related to the cleanup of connectors when a bridge is detached. This vulnerability was introduced in version v4.13 and has been fixed in version v5.12.4.
Vulnerability Detail
The cleanup connector on bridge detach vulnerability in the Kernel's bridge/panel module can potentially lead to security issues. When a bridge is detached, the connector cleanup process may not be properly executed, leaving behind remnants of the connector. This can result in various security risks, such as unauthorized access or privilege escalation. The impact and attack plausibility of this vulnerability have not been proven yet.
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 specific workaround has been mentioned for this vulnerability.
Conclusion
The cleanup connector on bridge detach vulnerability in the Kernel's bridge/panel module can pose potential security risks. It is crucial to update the Kernel to version v5.12.4 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it could potentially lead to unauthorized access or privilege escalation.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will alert you in real-time if the vulnerability is present.
As of now, there is no known exploit for this vulnerability. However, it is always recommended to apply security patches promptly to mitigate potential risks.
No, only versions starting from v4.13 up to v5.12.3 are affected. The vulnerability has been fixed in version v5.12.4.
Yes, if you are unable to update to the latest Kernel version, you can manually apply the patch provided in the commit 98d7d76a74e48ec3ddf2e23950adff7edcab9327. However, it is recommended to update to the latest version whenever possible.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
