Use-After-Free Vulnerability in Linux Kernel's vesafb Driver
Summary
CVE-2022-49419: In the Linux kernel, the following vulnerability has been resolved: video: fbdev: vesafb: Fix a use-after-free due early fb_info cleanup Commit b3c9a924aab6 ("fbdev: vesafb: Cleanup fb_info in .fb_destroy rather than .re... Affects linux versions < 5.18.5-1. Fixed in 5.18.5-1. 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 Linux kernel is a core component of many operating systems, providing essential services for hardware management and system operations. The vesafb driver is part of the framebuffer device (fbdev) subsystem, which allows for the management of graphics displays. This driver is responsible for handling the framebuffer interface for video output, enabling graphical user interfaces and rendering. However, it has been identified to have a use-after-free vulnerability that can lead to system instability or crashes.
Vulnerability Detail
In the Linux kernel, a use-after-free vulnerability was discovered in the vesafb driver. This issue arises when the fb_info structure is freed in the .remove callback before the .fb_destroy callback is executed. If the .fb_destroy callback is called after the .remove callback, it attempts to access a pointer that has already been freed, leading to potential system crashes or exploitation. The vulnerability can also occur if the .fb_destroy callback is executed before the .remove callback, particularly when no processes are using the framebuffer device at the time of driver removal.
How To Fix
Minimum fixed version
5.18.5-1
This is the first release that contains the fix.
sudo apt-get install --only-upgrade linuxTip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
Currently, there are no specific workarounds provided for this vulnerability. The best course of action is to apply the patch by updating the package as mentioned above.
Conclusion
The use-after-free vulnerability in the Linux kernel's vesafb driver poses significant risks to system stability and security. It is crucial for users to update their systems to the patched version to mitigate these risks. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for linux →
FAQ
A use-after-free vulnerability occurs when a program continues to use a pointer after the memory it points to has been freed, potentially leading to crashes or exploitation.
You can use Vulert, which monitors open-source vulnerabilities in your software. By uploading your manifest file like package-lock.json, you can check for vulnerabilities in real-time.
Exploiting this vulnerability can lead to system crashes, instability, or unauthorized access to system resources.
The vulnerability affects the Linux kernel versions prior to 5.18.5-1 in Debian:12 and Debian:13.
You can use tools like Vulert to monitor your software for vulnerabilities and receive alerts in real-time.
Related vulnerabilities
Recent vulnerabilities recorded for linux.
