Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-39801: usb: dwc3: Remove WARN_ON for device endpoint command timeouts

MediumCVSS 5.5 · v3.1—No exploit Fix available

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.15% (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 45eae113dccaf8e502090ecf5b3d9e9b805add6f, 5a1a847d841505dba2bd85602daf5c218e1d85b8, 84c95dbf5bece56086cdb65a64162af35158bdd9; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1.

Low priority for now. Upgrade to Linux Linux 45eae113dccaf8e502090ecf5b3d9e9b805add6f, 5a1a847d841505dba2bd85602daf5c218e1d85b8, 84c95dbf5bece56086cdb65a64162af35158bdd9; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1 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: Remove WARN_ON for device endpoint command timeouts This commit addresses a rarely observed endpoint command timeout which causes kernel panic due to warn when 'panic_on_warn' is enabled and unnecessary call trace prints when 'panic_on_warn' is disabled. It is seen during fast software-controlled connect/disconnect testcases. The following is one such endpoint command timeout that we observed: 1. Connect ======= ->dwc3_thread_interrupt ->dwc3_ep0_interrupt ->configfs_composite_setup ->composite_setup ->usb_ep_queue ->dwc3_gadget_ep0_queue ->__dwc3_gadget_ep0_queue ->__dwc3_ep0_do_control_data ->dwc3_send_gadget_ep_cmd 2. Disconnect ========== ->dwc3_thread_interrupt ->dwc3_gadget_disconnect_interrupt ->dwc3_ep0_reset_state ->dwc3_ep0_end_control_data ->dwc3_send_gadget_ep_cmd In the issue scenario, in Exynos platforms, we observed that control transfers for the previous connect have not yet been completed and end transfer command sent as a part of the disconnect sequence and processing of USB_ENDPOINT_HALT feature request from the host timeout. This maybe an expected scenario since the controller is processing EP commands sent as a part of the previous connect. It maybe better to remove WARN_ON in all places where device endpoint commands are sent to avoid unnecessary kernel panic due to warn.

Published
Sep 15, 2025
Updated
Nov 5, 2026
EPSS
0.1% · 5th percentile

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.1%

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-2025-39801

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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
debiandebian linux

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

    • 3.2affected
    • 72246da40f3719af3bfd104a2365b32537c27d83 and later · before dfe40159eec6ca63b40133bfa783eee2e3ed829faffected · git
    • 72246da40f3719af3bfd104a2365b32537c27d83 and later · before 5a1a847d841505dba2bd85602daf5c218e1d85b8affected · git
    • 72246da40f3719af3bfd104a2365b32537c27d83 and later · before 84c95dbf5bece56086cdb65a64162af35158bdd9affected · git
    • 72246da40f3719af3bfd104a2365b32537c27d83 and later · before f49697dfba2915a9ff36f94604eb76fa61413929affected · git
    • 72246da40f3719af3bfd104a2365b32537c27d83 and later · before db27482b9db340402e05d4e9b75352bbaca51af2affected · git
    • 72246da40f3719af3bfd104a2365b32537c27d83 and later · before 45eae113dccaf8e502090ecf5b3d9e9b805add6faffected · git
    • before 3.2not affected · semver
    • 5.15.190 and later · up to and including 5.15.*not affected · semver
    • 6.1.149 and later · up to and including 6.1.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.153-16.1.153-1
Debian:13linuxbefore 6.12.48-16.12.48-1
Debian:14linuxbefore 6.16.5-16.16.5-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-2023-53262Sep 15, 2025 · f2fs: fix scheduling while atomic in decompression path
    31Monitor
  • ← EarlierCVE-2025-39800Sep 15, 2025 · btrfs: abort transaction on unexpected eb generation at btrfs_copy_root()
    22Monitor
  • Later →CVE-2025-39802Sep 15, 2025 · lib/crypto: arm/poly1305: Fix register corruption in no-SIMD contexts
    31Monitor

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 Linux45eae113dccaf8e502090ecf5b3d9e9b805add6fVendor (CNA)
Linux Linux5a1a847d841505dba2bd85602daf5c218e1d85b8Vendor (CNA)
Linux Linux84c95dbf5bece56086cdb65a64162af35158bdd9Vendor (CNA)
Linux Linuxdb27482b9db340402e05d4e9b75352bbaca51af2Vendor (CNA)
Linux Linuxdfe40159eec6ca63b40133bfa783eee2e3ed829fVendor (CNA)
Linux Linuxf49697dfba2915a9ff36f94604eb76fa61413929Vendor (CNA)
azl3 kernel 6.6.96.2-2 on Azure Linux 3.06.6.104.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.153-1 · Debian:12Package 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.

Variant candidates

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

  • CVE-2026-31739228 days apartcrypto: tegra - Add missing CRYPTO_ALG_ASYNC
    35Monitor
  • CVE-2026-52952282 days apartiommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset
    35Monitor
  • CVE-2025-398030 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()
    31Monitor
  • CVE-2026-31398200 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios
    31Monitor
  • CVE-2026-46117255 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()
    31Monitor
  • CVE-2023-52621538 days apartbpf: Check rcu_read_lock_trace_held() before calling bpf map helpers
    31Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

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)

CWE-617 · Reachable Assertion

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.

References

All records