[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025072504-CVE-2025-38376-e290@gregkh>
Date: Fri, 25 Jul 2025 14:55:07 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38376: usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume
Shawn and John reported a hang issue during system suspend as below:
- USB gadget is enabled as Ethernet
- There is data transfer over USB Ethernet (scp a big file between host
and device)
- Device is going in/out suspend (echo mem > /sys/power/state)
The root cause is the USB device controller is suspended but the USB bus
is still active which caused the USB host continues to transfer data with
device and the device continues to queue USB requests (in this case, a
delayed TCP ACK packet trigger the issue) after controller is suspended,
however the USB controller clock is already gated off. Then if udc driver
access registers after that point, the system will hang.
The correct way to avoid such issue is to disconnect device from host when
the USB bus is not at suspend state. Then the host will receive disconnect
event and stop data transfer in time. To continue make USB gadget device
work after system resume, this will reconnect device automatically.
To make usb wakeup work if USB bus is already at suspend state, this will
keep connection for it only when USB device controller has enabled wakeup
capability.
The Linux kernel CVE team has assigned CVE-2025-38376 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.2 with commit 235ffc17d0146d806f6ad8c094c24ff4878f2edb and fixed in 6.6.97 with commit 937f49be49d6ee696eb5457c21ff89c135c9b5ae
Issue introduced in 6.2 with commit 235ffc17d0146d806f6ad8c094c24ff4878f2edb and fixed in 6.12.37 with commit c68a27bbebbdb4e0ccd45d4f0df7111a09ddac24
Issue introduced in 6.2 with commit 235ffc17d0146d806f6ad8c094c24ff4878f2edb and fixed in 6.15.6 with commit 5fd585fedb79bac2af9976b0fa3ffa354f0cc0bb
Issue introduced in 6.2 with commit 235ffc17d0146d806f6ad8c094c24ff4878f2edb and fixed in 6.16-rc5 with commit 31a6afbe86e8e9deba9ab53876ec49eafc7fd901
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-38376
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/usb/chipidea/udc.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/937f49be49d6ee696eb5457c21ff89c135c9b5ae
https://git.kernel.org/stable/c/c68a27bbebbdb4e0ccd45d4f0df7111a09ddac24
https://git.kernel.org/stable/c/5fd585fedb79bac2af9976b0fa3ffa354f0cc0bb
https://git.kernel.org/stable/c/31a6afbe86e8e9deba9ab53876ec49eafc7fd901
Powered by blists - more mailing lists