fbmem: Do not delete the mode that is still in use in Kernel
Summary
GSD-2021-1001211: fbmem: Do not delete the mode that is still in use. Affects Kernel versions >= 13ff178ccd6d3b8074c542a911300b79c4eec255, < d6e76469157d8f240e5dec6f8411aa8d306b1126. 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 critical component of the Linux operating system that manages the system's resources and facilitates communication between hardware and software. It provides essential functions such as process management, memory management, and device drivers. The fbmem module in the Kernel is responsible for managing the frame buffer memory, which is used for displaying graphics on the screen. This vulnerability in the fbmem module allows the deletion of a mode that is still in use, leading to potential system instability and crashes.
Vulnerability Detail
The vulnerability arises from a flaw in the fbmem module of the Kernel. When attempting to delete a mode that is still in use, the module fails to properly handle this situation, resulting in a system state where the mode is no longer available but still being referenced. This can lead to various issues, including graphical glitches, system freezes, and even denial of service if exploited maliciously. The vulnerability was introduced in Kernel version v5.3 and is fixed in version v5.13.4.
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
As a temporary workaround, users can avoid triggering the vulnerability by refraining from deleting modes that are currently in use. This can be achieved by carefully managing the frame buffer configuration and ensuring that no active modes are deleted. However, this workaround may not be feasible in all scenarios and does not provide a permanent solution to the vulnerability.
Conclusion
The fbmem module in the Kernel is vulnerable to a flaw that allows the deletion of a mode that is still in use. This can lead to system instability and crashes. It is recommended to update the Kernel to version v5.13.4 or later to fix this vulnerability. Users can also utilize the Vulert Playground (https://vulert.com/scanner) to check if their system is affected and take appropriate actions. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can result in system instability, graphical glitches, system freezes, and potential denial of service if exploited maliciously.
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 the tool will analyze it for any known vulnerabilities.
Yes, the vulnerability is fixed in Kernel version v5.13.4. It is recommended to update to this version or a later one to mitigate the risk.
While there are no specific configuration changes to mitigate the vulnerability, users can follow best practices for system security, such as keeping the Kernel up to date and implementing proper access controls.
At the time of this report, there are no known public exploits targeting this vulnerability. However, it is important to apply the necessary updates to prevent any potential exploitation.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
