CVE-2021-47331: usb: common: usb-conn-gpio: fix NULL pointer dereference of charger
In the Linux kernel, the following vulnerability has been resolved:
usb: common: usb-conn-gpio: fix NULL pointer dereference of charger
When power on system with OTG cable, IDDIG's interrupt arises before
the charger registration, it will cause a NULL pointer dereference,
fix the issue by registering the power supply before requesting
IDDIG/VBUS irq.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash affected systems during power-on when a USB OTG cable is present and an interrupt occurs before charger registration completes. The source bundle does not provide CVSS, CWE, or confirmed business impact, so urgency depends on whether your Linux builds use this USB GPIO connector path.
Executive priority
Do not treat this as an emergency based on the supplied evidence. Assign targeted remediation to teams managing Linux kernels on OTG-capable devices, especially embedded or appliance products where boot reliability matters.
Technical view
CVE-2021-47331 is a NULL pointer dereference in usb-conn-gpio. The described race occurs when IDDIG interrupt handling can run before charger power-supply registration. The upstream fix changes initialization order by registering the power supply before requesting IDDIG/VBUS IRQs.
Likely exposure
Exposure appears limited to Linux systems using the usb-conn-gpio USB OTG connector driver on affected kernel versions or commits. Systems without this driver path, without relevant OTG hardware, or already carrying the referenced stable fixes are less likely exposed.
Exploitation context
The bundle reports no KEV listing and provides no evidence of active exploitation. The described trigger involves powering on with an OTG cable and an interrupt timing issue. Treat this as a potential local or physical-condition denial-of-service risk unless vendor evidence says otherwise.
Researcher notes
The public record lacks CVSS, CWE, and detailed exploitability analysis. The key evidence is the kernel commit description: IDDIG IRQ can precede charger registration, causing a NULL pointer dereference. Avoid broad exposure claims without confirming driver usage and fixed commit presence.
Mitigation direction
Check whether your kernel includes the referenced stable fixes.
Prioritize vendor-supported kernel updates for affected Linux builds.
Review device-tree and kernel configuration for usb-conn-gpio usage.
For embedded fleets, test boot behavior with OTG cables attached.
If no vendor advisory applies, monitor Linux stable guidance.
Validation and detection
Inventory Linux kernel versions across affected device classes.
Check kernel source or package changelog for the stable commit references.
Confirm whether usb-conn-gpio is built or loaded.
Test representative hardware booting with OTG cable attached.
Document unaffected platforms where this driver path is absent.
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-47331 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.