CVE-2025-39801

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.

• CWE-617

• https://git.kernel.org/stable/c/45eae113dccaf8e502090ecf5b3d9e9b805add6fPatch
• https://git.kernel.org/stable/c/5a1a847d841505dba2bd85602daf5c218e1d85b8Patch
• https://git.kernel.org/stable/c/84c95dbf5bece56086cdb65a64162af35158bdd9Patch
• https://git.kernel.org/stable/c/db27482b9db340402e05d4e9b75352bbaca51af2Patch
• https://git.kernel.org/stable/c/dfe40159eec6ca63b40133bfa783eee2e3ed829fPatch
• https://git.kernel.org/stable/c/f49697dfba2915a9ff36f94604eb76fa61413929Patch
• https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlThird Party Advisory
• https://cert-portal.siemens.com/productcert/html/ssa-032379.html

Published

Sep 15, 2025

Last Modified

Jun 17, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2025-39796In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-39797In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-39798In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39799Rejected reason: This CVE ID has been rejected or withdrawn …
• CVE-2025-3980A vulnerability classified as problematic was found in wowjo…5.3
• CVE-2025-39800In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39802In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-39803In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-39804In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-39805In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39806In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2025-39807In the Linux kernel, the following vulnerability has been re…5.5