CVE-2021-47471: drm: mxsfb: Fix NULL pointer dereference crash on unload
In the Linux kernel, the following vulnerability has been resolved:
drm: mxsfb: Fix NULL pointer dereference crash on unload
The mxsfb->crtc.funcs may already be NULL when unloading the driver,
in which case calling mxsfb_irq_disable() via drm_irq_uninstall() from
mxsfb_unload() leads to NULL pointer dereference.
Since all we care about is masking the IRQ and mxsfb->base is still
valid, just use that to clear and mask the IRQ.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel availability bug in the mxsfb display driver. When the driver is unloaded, a NULL pointer dereference can crash the system. The practical business impact is local denial of service, not data theft or remote compromise based on the supplied evidence.
Executive priority
Treat as a normal-priority kernel availability fix unless affected embedded or display-dependent systems have high uptime requirements. There is no supplied evidence of remote compromise or active exploitation.
Technical view
The flaw is CWE-476 in Linux DRM mxsfb unload handling. If mxsfb->crtc.funcs is already NULL, drm_irq_uninstall() can call mxsfb_irq_disable() and dereference NULL. Stable fixes mask the IRQ using mxsfb->base, which remains valid.
Likely exposure
Exposure appears limited to Linux systems running affected kernels with the mxsfb DRM driver present and reachable through driver unload paths. The supplied version data is incomplete and should be checked against distributor kernel advisories and backports.
Exploitation context
CVSS shows local attack vector, low complexity, low privileges, no user interaction, and high availability impact. The bundle says KEV is false, and no cited source states active exploitation.
Researcher notes
The record identifies a crash-on-unload condition and three stable kernel references. Affected version boundaries in the supplied bundle are not fully normalized, so validation should rely on exact kernel package provenance and vendor backport status.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Check distribution advisories for backported fixes before relying on upstream version numbers.
Avoid unloading the mxsfb driver on affected systems until patched.
Restrict local access capable of triggering driver or module unload behavior.
Validation and detection
Inventory Linux kernel versions on systems using the mxsfb DRM driver.
Check whether mxsfb is built, loaded, or operationally required.
Compare vendor kernel packages against the referenced stable commits.
Confirm monitoring covers unexpected kernel crashes or display-driver unload events.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.