Null Pointer Dereference Crash in drm: mxsfb
Summary
GSD-2021-1002051: drm: mxsfb: Fix NULL pointer dereference crash on unload. Affects Kernel versions >= ae1ed0093281939b80664a687689f12436c0e874, < f40c2281d2c0674d32ba732fee45222d76495472. 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 (Direct Rendering Manager) is a subsystem in the Linux kernel responsible for managing graphics drivers and rendering. The mxsfb driver is specifically designed for the MXS SoC framebuffer driver. This vulnerability affects the Linux Kernel package.
Vulnerability Detail
The vulnerability in the drm: mxsfb driver leads to a null pointer dereference crash during the unload process. This occurs when a null pointer is accessed, causing the system to crash. The impact and plausibility of an attack have not been proven yet. The vulnerability was introduced in Linux Kernel version v5.10 by commit ae1ed0093281939b80664a687689f12436c0e874 and fixed in version v5.10.76 by commit f40c2281d2c0674d32ba732fee45222d76495472.
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 null pointer dereference crash vulnerability in the drm: mxsfb driver can be fixed by updating the Linux Kernel package to version v5.10.76 or later. It is recommended to apply the update as soon as possible to ensure the security and stability of the system. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a null pointer dereference crash, causing the system to become unresponsive or crash.
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 it will alert you in real-time.
No known exploit has been reported for this vulnerability at this time.
The recommended mitigation is to update the Linux Kernel package to the fixed version.
The remote exploitability of this vulnerability has not been determined yet.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
