CVE-2021-47233: regulator: rt4801: Fix NULL pointer dereference if priv->enable_gpios is NULL
In the Linux kernel, the following vulnerability has been resolved:
regulator: rt4801: Fix NULL pointer dereference if priv->enable_gpios is NULL
devm_gpiod_get_array_optional may return NULL if no GPIO was assigned.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47233 is a Linux kernel driver bug that may crash affected systems in specific RT4801 regulator configurations. The issue is a NULL pointer dereference when optional GPIO data is absent. The provided sources do not show remote code execution, privilege escalation, CVSS scoring, or active exploitation.
Executive priority
Treat this as a targeted kernel maintenance issue unless affected RT4801-based systems are business critical. There is no sourced evidence of active exploitation, but kernel crashes can affect availability. Patch through normal vendor kernel update processes after exposure is confirmed.
Technical view
The Linux kernel RT4801 regulator driver called devm_gpiod_get_array_optional, which can return NULL when no GPIO is assigned. The driver then dereferenced priv->enable_gpios. Stable kernel commits resolve the flaw by handling the NULL case. Source data identifies affected Linux kernel versions around 5.10 through 5.13, including fixed points 5.10.46 and 5.12.13.
Likely exposure
Exposure appears limited to Linux systems using affected kernels with the RT4801 regulator driver and no assigned enable GPIO. General Linux deployments may not be exposed if the driver or hardware path is absent. Distribution backports may change practical exposure.
Exploitation context
The source bundle does not cite exploitation in the wild, KEV listing, public exploit activity, or exploit prerequisites. The described failure mode is a kernel NULL pointer dereference, most likely affecting availability in a specific hardware or driver configuration.
Researcher notes
Evidence is concise and kernel-commit based. The CVE record lacks CVSS, CWE, detailed exploitability, and operational prerequisites. Avoid broad claims beyond affected kernel versions and the RT4801 regulator NULL dereference fixed in stable commits.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Check distribution advisories for backported fixes and supported kernel packages.
Prioritize systems using kernels in the affected 5.10 through 5.13 range.
If updates are unavailable, consult vendor guidance for RT4801 driver exposure.
Do not assume generic Linux systems are exposed without driver and hardware evidence.
Validation and detection
Inventory running kernel versions and vendor patch levels.
Confirm whether the RT4801 regulator driver is present or enabled.
Review vendor changelogs for the referenced stable commit IDs.
Check device configuration for RT4801 regulator and enable GPIO usage.
Monitor kernel logs for related NULL dereference or regulator driver faults.
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.
cve · low confidence lookup
CVE-2021-47233 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.