LiveActive security incident?Get immediate response
CVE Record

CVE-2021-46941: usb: dwc3: core: Do core softreset when switch mode

In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: core: Do core softreset when switch mode According to the programming guide, to switch mode for DRD controller, the driver needs to do the following. To switch from device to host: 1. Reset controller with GCTL.CoreSoftReset 2. Set GCTL.PrtCapDir(host mode) 3. Reset the host with USBCMD.HCRESET 4. Then follow up with the initializing host registers sequence To switch from host to device: 1. Reset controller with GCTL.CoreSoftReset 2. Set GCTL.PrtCapDir(device mode) 3. Reset the device with DCTL.CSftRst 4. Then follow up with the initializing registers sequence Currently we're missing step 1) to do GCTL.CoreSoftReset and step 3) of switching from host to device. John Stult reported a lockup issue seen with HiKey960 platform without these steps[1]. Similar issue is observed with Ferry's testing platform[2]. So, apply the required steps along with some fixes to Yu Chen's and John Stultz's version. The main fixes to their versions are the missing wait for clocks synchronization before clearing GCTL.CoreSoftReset and only apply DCTL.CSftRst when switching from host to device. [1] https://lore.kernel.org/linux-usb/20210108015115.27920-1-john.stultz@linaro.org/ [2] https://lore.kernel.org/linux-usb/0ba7a6ba-e6a7-9cd4-0695-64fc927e01f1@gmail.com/

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause systems with certain USB dual-role controllers to lock up when switching USB mode. The public record ties observed failures to HiKey960 and another testing platform. It is mainly an availability and stability concern, not a confirmed remote compromise issue.

Executive priority

Treat as targeted operational risk for affected Linux-based devices, not an internet-wide emergency. Prioritize products where USB role switching is used and lockups affect service reliability, safety, or field support costs.

Technical view

The dwc3 core driver missed required GCTL.CoreSoftReset handling during DRD host/device mode changes, and missed DCTL.CSftRst when switching host to device. The fix adds the documented reset sequencing and clock-synchronization wait. Affected exposure depends on Linux kernel branch, backports, and DWC3 dual-role USB hardware use.

Likely exposure

Likely limited to Linux systems using the DWC3 USB dual-role controller path, especially embedded or mobile-class platforms. The source identifies affected Linux kernel ranges and stable commits, but does not provide complete distribution package mappings.

Exploitation context

No active exploitation is identified in the provided sources, and CISA KEV status is false. The cited impact is lockup during USB role switching. The bundle does not describe a remote attack path or public exploit.

Researcher notes

Evidence supports a kernel driver sequencing bug resolved by stable commits. Severity, CVSS, CWE, and distribution mappings are absent in the bundle. Analysis should focus on kernel provenance, DWC3 DRD configuration, and vendor backport confirmation.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes or vendor backport.
  • Check Linux distribution advisories for package-specific fixed versions.
  • Prioritize embedded systems using DWC3 USB dual-role mode.
  • Avoid direct deployment changes without normal regression testing.

Validation and detection

  • Inventory systems using DWC3 dual-role USB controller functionality.
  • Compare running kernel versions and commits against vendor fixed builds.
  • Review device logs for lockups during USB host/device switching.
  • Confirm the referenced reset-sequencing patch is present in custom kernels.
Prepared
Confidence
medium
Sources
6

Public sources used

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-46941 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux41ce1456e1dbbc7355d0fcc10cf7c337c13def24, 41ce1456e1dbbc7355d0fcc10cf7c337c13def24, 41ce1456e1dbbc7355d0fcc10cf7c337c13def24, 41ce1456e1dbbc7355d0fcc10cf7c337c13def24unaffected
LinuxLinux4.12, 0, 5.10.36, 5.11.20, 5.12.3, 5.13affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.