Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2025-39801

medium

In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: Remove WARN_ON for device endpoint command timeouts This commit addresses a ra…

Vendor / product: Linux — linux kernel

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.

CVSS
5.5
5.5 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2025-09-15 13:15
Modified: 2026-11-05 22:17
NVD status: Modified
Last synced 1 week ago
Verified against the source API 2026-11-05 22:23 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥3.2 <5.15.190, ≥5.16 <6.1.149, ≥6.2 <6.6.103, ≥6.7 <6.12.44, ≥6.13 <6.16.4, 6.17
debian / debian_linux 11.0

Weakness classification (CWE)

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/45eae113dccaf8e502090ecf5b3d9e9b805add6f
Patch / mitigation: https://git.kernel.org/stable/c/5a1a847d841505dba2bd85602daf5c218e1d85b8
Patch / mitigation: https://git.kernel.org/stable/c/84c95dbf5bece56086cdb65a64162af35158bdd9
Patch / mitigation: https://git.kernel.org/stable/c/db27482b9db340402e05d4e9b75352bbaca51af2
Patch / mitigation: https://git.kernel.org/stable/c/dfe40159eec6ca63b40133bfa783eee2e3ed829f
Patch / mitigation: https://git.kernel.org/stable/c/f49697dfba2915a9ff36f94604eb76fa61413929

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-05 22:23 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs