NULL pointer dereference crash in drm: mxsfb

Kernel Updated 02 Oct 2025

Summary

14/11/2021
N/A
No i
Unrated
Not published

GSD-2021-1002183: drm: mxsfb: Fix NULL pointer dereference crash on unload. Affects Kernel versions >= ae1ed0093281939b80664a687689f12436c0e874, < 3cfc183052c3dbf8eae57b6c1685dab00ed3db4a. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The drm (Direct Rendering Manager) subsystem in the Linux Kernel is responsible for managing graphics drivers and providing an interface between user-space applications and the underlying hardware. The mxsfb driver is specifically designed for the MXS SoC framebuffer driver. It allows for the display of graphics on devices that utilize the MXS SoC (System-on-Chip) architecture. The vulnerability in question involves a NULL pointer dereference crash that occurs during the unload process of the mxsfb driver.

Vulnerability Detail

The vulnerability arises due to a NULL pointer dereference in the mxsfb driver during the unload process. When unloading the driver, a NULL pointer is accessed, leading to a crash. An attacker with local access to the system could potentially exploit this vulnerability to cause a denial-of-service (DoS) condition, resulting in a system crash. The impact and attack plausibility of this vulnerability have not been proven yet.

How To Fix

No fixed version is published for this vulnerability.

The vulnerability has been fixed in the Linux Kernel version v5.15 by commit 3cfc183052c3dbf8eae57b6c1685dab00ed3db4a. To fix the vulnerability, users are advised to update their Linux Kernel to version v5.15 or later. This can be done by obtaining the updated kernel source code and compiling it, or by using package managers or update mechanisms provided by the Linux distribution being used.

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 has been addressed in the Linux Kernel version v5.15. Users are advised to update their kernel to the latest version to mitigate the risk of exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can potentially lead to a system crash, resulting in a denial-of-service (DoS) condition.

An attacker with local access to the system can potentially exploit this vulnerability.

No, the impact and attack plausibility of this vulnerability have not been proven yet.

To fix the vulnerability, update your Linux Kernel to version v5.15 or later.

No, no workaround has been provided for this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

The vulnerability has been fixed in the Linux Kernel version v5.15 by commit 3cfc183052c3dbf8eae57b6c1685dab00ed3db4a. To fix the vulnerability, users are advised to update their Linux Kernel to version v5.15 or later. This can be done by obtaining the updated kernel source code and compiling it, or by using package managers or update mechanisms provided by the Linux distribution being used.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.