[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2026011301-CVE-2025-68781-f30f@gregkh>
Date: Tue, 13 Jan 2026 16:29:07 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68781: usb: phy: fsl-usb: Fix use-after-free in delayed work during device removal
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
usb: phy: fsl-usb: Fix use-after-free in delayed work during device removal
The delayed work item otg_event is initialized in fsl_otg_conf() and
scheduled under two conditions:
1. When a host controller binds to the OTG controller.
2. When the USB ID pin state changes (cable insertion/removal).
A race condition occurs when the device is removed via fsl_otg_remove():
the fsl_otg instance may be freed while the delayed work is still pending
or executing. This leads to use-after-free when the work function
fsl_otg_event() accesses the already freed memory.
The problematic scenario:
(detach thread) | (delayed work)
fsl_otg_remove() |
kfree(fsl_otg_dev) //FREE| fsl_otg_event()
| og = container_of(...) //USE
| og-> //USE
Fix this by calling disable_delayed_work_sync() in fsl_otg_remove()
before deallocating the fsl_otg structure. This ensures the delayed work
is properly canceled and completes execution prior to memory deallocation.
This bug was identified through static analysis.
The Linux kernel CVE team has assigned CVE-2025-68781 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.0 with commit 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 and fixed in 6.1.160 with commit 4476c73bbbb09b13a962176fca934b32d3954a2e
Issue introduced in 3.0 with commit 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 and fixed in 6.6.120 with commit 319f7a85b3c4e34ac2fe083eb146fe129a556317
Issue introduced in 3.0 with commit 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 and fixed in 6.12.64 with commit 69f9a0701abc3d1f8225074c56c27e6c16a37222
Issue introduced in 3.0 with commit 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 and fixed in 6.18.3 with commit 2e7c47e2eb3cfeadf78a1ccbac8492c60d508f23
Issue introduced in 3.0 with commit 0807c500a1a6d7fa20cbd7bbe7fea14a66112463 and fixed in 6.19-rc3 with commit 41ca62e3e21e48c2903b3b45e232cf4f2ff7434f
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-68781
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/phy/phy-fsl-usb.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/4476c73bbbb09b13a962176fca934b32d3954a2e
https://git.kernel.org/stable/c/319f7a85b3c4e34ac2fe083eb146fe129a556317
https://git.kernel.org/stable/c/69f9a0701abc3d1f8225074c56c27e6c16a37222
https://git.kernel.org/stable/c/2e7c47e2eb3cfeadf78a1ccbac8492c60d508f23
https://git.kernel.org/stable/c/41ca62e3e21e48c2903b3b45e232cf4f2ff7434f
Powered by blists - more mailing lists