From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-93225: phy: fsl-imx8mq-usb: fix typec switch leak on probe error path
Date: Thu, 24 Sep 2026 17:21:09 +0200 [thread overview]
Message-ID: <2026092407-CVE-2026-93225-52e4@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
phy: fsl-imx8mq-usb: fix typec switch leak on probe error path
If probe fails after imx95_usb_phy_get_tca() succeeds, the typec
switch leaks because the only cleanup path was in .remove(), which
never runs on probe failure.
Use devm_add_action_or_reset() so the switch is cleaned up on both
probe failure and driver removal. The imx95_usb_phy_put_tca() is no
longer needed, it will be removed in .remove() too.
The Linux kernel CVE team has assigned CVE-2026-93225 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.15 with commit b58f0f86fd6156d7b084257f5c91ceaf7d760927 and fixed in 6.18.50 with commit f1b7b2c7ffa9711d1298f52790b377fe02efc1db
Issue introduced in 6.15 with commit b58f0f86fd6156d7b084257f5c91ceaf7d760927 and fixed in 7.2.4 with commit 84646f5b945a370f6999eed59a334387b0abc282
Issue introduced in 6.15 with commit b58f0f86fd6156d7b084257f5c91ceaf7d760927 and fixed in 7.3-rc1 with commit 87a1805b1c346b092c34f96f3806f207792910e1
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-2026-93225
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/phy/freescale/phy-fsl-imx8mq-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/f1b7b2c7ffa9711d1298f52790b377fe02efc1db
https://git.kernel.org/stable/c/84646f5b945a370f6999eed59a334387b0abc282
https://git.kernel.org/stable/c/87a1805b1c346b092c34f96f3806f207792910e1
reply other threads:[~2026-09-24 15:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026092407-CVE-2026-93225-52e4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.