fbdev: Fix unregistering of framebuffers without device
Summary
GSD-2022-1001672: fbdev: Fix unregistering of framebuffers without device. Affects Kernel versions >= c894ac44786cfed383a6c6b20c1bfb12eb96018a, < 2388f826cdc9af2651991adc0feb79de9bdf2232. 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 fbdev package is a component of the Linux Kernel that provides support for frame buffer devices. Frame buffer devices are used to display graphics and images on computer screens. The package includes functions and drivers that allow applications to interact with the frame buffer devices. This vulnerability affects the unregistering of framebuffers without a device, which can lead to potential security issues.
Vulnerability Detail
The vulnerability in the fbdev package arises from a flaw in the unregistering process of framebuffers when there is no associated device. This flaw can be exploited by an attacker to cause a denial-of-service (DoS) condition or potentially execute arbitrary code. By unregistering framebuffers without a device, the system may become unstable or crash, leading to a loss of availability. The vulnerability was introduced in version v5.15.33 of the Linux Kernel and has been fixed in version v5.15.34.
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 →
Conclusion
The fbdev package in the Linux Kernel is vulnerable to a flaw in the unregistering process of framebuffers without a device. This vulnerability can lead to a denial-of-service condition or potential code execution. It is crucial to update to the fixed version of the Linux Kernel (v5.15.34 or later) to mitigate these risks. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a denial-of-service condition or potential code execution, which may result in system instability or crashes.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
No specific workaround has been provided for this vulnerability. It is recommended to update to the fixed version of the Linux Kernel.
At the time of this report, no known exploits for this vulnerability have been reported. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
You can find more information about this vulnerability in the official Linux Kernel repository or through the provided source link in the vulnerability details.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
