Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1c10fd60c8595ea7ff7e29d3cf1fa88069941da3, 800f58217626c8b147aa40660e572ed8a0d56e3b, f88359e1588b85cf0e8209ab7d6620085f3441d9.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1c10fd60c8595ea7ff7e29d3cf1fa88069941da3, 800f58217626c8b147aa40660e572ed8a0d56e3b, f88359e1588b85cf0e8209ab7d6620085f3441d9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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/

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 27, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 13th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-46941

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.12.0 and later · before 5.10.36
  • linux linux kernel5.11.0 and later · before 5.11.20
  • linux linux kernel5.12.0 and later · before 5.12.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.12affected
    • 41ce1456e1dbbc7355d0fcc10cf7c337c13def24 and later · before fce7bbcd07d59ac30dba8ce225316b3b4c1c7b50affected · git
    • 41ce1456e1dbbc7355d0fcc10cf7c337c13def24 and later · before 800f58217626c8b147aa40660e572ed8a0d56e3baffected · git
    • 41ce1456e1dbbc7355d0fcc10cf7c337c13def24 and later · before 1c10fd60c8595ea7ff7e29d3cf1fa88069941da3affected · git
    • 41ce1456e1dbbc7355d0fcc10cf7c337c13def24 and later · before f88359e1588b85cf0e8209ab7d6620085f3441d9affected · git
    • before 4.12not affected · semver
    • 5.10.36 and later · up to and including 5.10.*not affected · semver
    • 5.11.20 and later · up to and including 5.11.*not affected · semver
    • 5.12.3 and later · up to and including 5.12.*not affected · semver
    • 5.13 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.10.38-15.10.38-1
SUSE:Linux Enterprise High Availability Extension 12 SP5kernel-defaultbefore 4.12.14-122.216.14.12.14-122.216.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_56before 1-8.3.11-8.3.1
SUSE:Linux Enterprise Real Time 12 SP5kernel-rtbefore 4.12.14-10.182.14.12.14-10.182.1
SUSE:Linux Enterprise Real Time 12 SP5kernel-rt_debugbefore 4.12.14-10.182.14.12.14-10.182.1
SUSE:Linux Enterprise Real Time 12 SP5kernel-source-rtbefore 4.12.14-10.182.14.12.14-10.182.1
SUSE:Linux Enterprise Real Time 12 SP5kernel-syms-rtbefore 4.12.14-10.182.14.12.14-10.182.1
SUSE:Linux Enterprise Server 12 SP5kernel-azurebefore 4.12.14-16.182.14.12.14-16.182.1
SUSE:Linux Enterprise Server 12 SP5kernel-sourcebefore 4.12.14-122.216.14.12.14-122.216.1
SUSE:Linux Enterprise Server 12 SP5kernel-source-azurebefore 4.12.14-16.182.14.12.14-16.182.1
SUSE:Linux Enterprise Server 12 SP5kernel-symsbefore 4.12.14-122.216.14.12.14-122.216.1
SUSE:Linux Enterprise Server 12 SP5kernel-syms-azurebefore 4.12.14-16.182.14.12.14-16.182.1
SUSE:Linux Enterprise Software Development Kit 12 SP5kernel-docsbefore 4.12.14-122.216.14.12.14-122.216.1
SUSE:Linux Enterprise Software Development Kit 12 SP5kernel-obs-buildbefore 4.12.14-122.216.14.12.14-122.216.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2021-46939Feb 27, 2024 · tracing: Restructure trace_clock_global() to never block
    22Monitor
  • ← EarlierCVE-2021-46940Feb 27, 2024 · tools/power turbostat: Fix offset overflow issue in index converting
    22Monitor
  • Later →CVE-2021-46942Feb 27, 2024 · io_uring: fix shared sqpoll cancellation hangs
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1c10fd60c8595ea7ff7e29d3cf1fa88069941da3Vendor (CNA)
Linux Linux800f58217626c8b147aa40660e572ed8a0d56e3bVendor (CNA)
Linux Linuxf88359e1588b85cf0e8209ab7d6620085f3441d9Vendor (CNA)
Linux Linuxfce7bbcd07d59ac30dba8ce225316b3b4c1c7b50Vendor (CNA)
debian:linux5.10.38-1 · Debian:12Package registry (OSV)
suse:kernel-azure4.12.14-16.182.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:kernel-default4.12.14-122.216.1 · SUSE:Linux Enterprise High Availability Extension 12 SP5Package registry (OSV)
suse:kernel-docs4.12.14-122.216.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5Package registry (OSV)
suse:kernel-obs-build4.12.14-122.216.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5Package registry (OSV)
suse:kernel-rt4.12.14-10.182.1 · SUSE:Linux Enterprise Real Time 12 SP5Package registry (OSV)
suse:kernel-rt_debug4.12.14-10.182.1 · SUSE:Linux Enterprise Real Time 12 SP5Package registry (OSV)
suse:kernel-source4.12.14-122.216.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:kernel-source-azure4.12.14-16.182.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:kernel-source-rt4.12.14-10.182.1 · SUSE:Linux Enterprise Real Time 12 SP5Package registry (OSV)
suse:kernel-syms-azure4.12.14-16.182.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:kernel-syms-rt4.12.14-10.182.1 · SUSE:Linux Enterprise Real Time 12 SP5Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_561-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records