CVE-2021-47409: usb: dwc2: check return value after calling platform_get_resource()
In the Linux kernel, the following vulnerability has been resolved:
usb: dwc2: check return value after calling platform_get_resource()
It will cause null-ptr-deref if platform_get_resource() returns NULL,
we need check the return value.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47409 is a Linux kernel flaw in the USB dwc2 driver. If a required platform resource lookup fails, the driver can dereference a null pointer and crash kernel code. The public record does not provide CVSS, confirmed exploit activity, or detailed real-world impact beyond the null-pointer dereference.
Executive priority
Treat this as a targeted kernel availability issue, not a confirmed internet-scale emergency. Prioritize patch tracking for embedded, appliance, and USB-dependent Linux assets, especially where outages would affect operations.
Technical view
The dwc2 USB driver called platform_get_resource() without validating a NULL return. The kernel fix adds return-value checking to avoid a null-pointer dereference. The affected data lists Linux kernel versions including 4.11 and stable lines around 4.14.250, 4.19.210, 5.4.152, 5.10.72, 5.14.11, and 5.15.
Likely exposure
Exposure is most likely on Linux systems that include and use the dwc2 USB driver, commonly tied to USB OTG/controller support. The source bundle does not identify specific distributions, devices, appliances, or cloud platforms.
Exploitation context
The CVE is not listed as KEV in the provided bundle. No cited source confirms active exploitation or public exploit availability. Based on the description, the known consequence is a null-pointer dereference, which usually maps to availability risk rather than data theft.
Researcher notes
Evidence is limited to the CVE record and Linux stable commit references. The bundle does not include CVSS, CWE, exploitability detail, attack prerequisites, or distribution advisories. Avoid assuming remote reachability or broad exploitability without device-specific validation.
Mitigation direction
Update to a Linux kernel containing the referenced stable fixes.
Use distribution or device-vendor kernel packages rather than self-selecting commits when possible.
Check vendor advisories for backported fixes on supported kernel branches.
Prioritize systems where dwc2 USB support is enabled and operationally important.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and embedded devices.
Check whether the dwc2 driver is present, built, or loaded.
Compare vendor kernel changelogs against the referenced upstream stable commits.
Confirm patched kernels boot and USB functions still work in regression testing.
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-47409 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.