From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43426: usb: renesas_usbhs: fix use-after-free in ISR during device removal
Date: Fri, 8 May 2026 16:22:35 +0200 [thread overview]
Message-ID: <2026050849-CVE-2026-43426-eef1@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
usb: renesas_usbhs: fix use-after-free in ISR during device removal
In usbhs_remove(), the driver frees resources (including the pipe array)
while the interrupt handler (usbhs_interrupt) is still registered. If an
interrupt fires after usbhs_pipe_remove() but before the driver is fully
unbound, the ISR may access freed memory, causing a use-after-free.
Fix this by calling devm_free_irq() before freeing resources. This ensures
the interrupt handler is both disabled and synchronized (waits for any
running ISR to complete) before usbhs_pipe_remove() is called.
The Linux kernel CVE team has assigned CVE-2026-43426 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.0 with commit f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and fixed in 5.10.253 with commit c7012fc73dab4829404fedeeaa8531f12ac8545f
Issue introduced in 3.0 with commit f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and fixed in 5.15.203 with commit 51afaf919bbaacdd9cc9e146033ae0a743a42dd7
Issue introduced in 3.0 with commit f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and fixed in 6.1.167 with commit 1899edac312ef17a7234851686e8a703f56d0a84
Issue introduced in 3.0 with commit f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and fixed in 6.6.130 with commit 9c6159d5b72d5fc265cce5da04f27d730b552e69
Issue introduced in 3.0 with commit f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and fixed in 6.12.78 with commit 6287e0c01ccb818e7214f88d885ffb7c9e81b0e0
Issue introduced in 3.0 with commit f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and fixed in 6.18.19 with commit 0b7d11fd6e742ecc0b1eca44b4f0b93140c74bae
Issue introduced in 3.0 with commit f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and fixed in 6.19.9 with commit 6ffe44f022c95b1b29c691d2169c5abc046f7580
Issue introduced in 3.0 with commit f1407d5c66240b33d11a7f1a41d55ccf6a9d7647 and fixed in 7.0 with commit 3cbc242b88c607f55da3d0d0d336b49bf1e20412
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-43426
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/renesas_usbhs/common.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/c7012fc73dab4829404fedeeaa8531f12ac8545f
https://git.kernel.org/stable/c/51afaf919bbaacdd9cc9e146033ae0a743a42dd7
https://git.kernel.org/stable/c/1899edac312ef17a7234851686e8a703f56d0a84
https://git.kernel.org/stable/c/9c6159d5b72d5fc265cce5da04f27d730b552e69
https://git.kernel.org/stable/c/6287e0c01ccb818e7214f88d885ffb7c9e81b0e0
https://git.kernel.org/stable/c/0b7d11fd6e742ecc0b1eca44b4f0b93140c74bae
https://git.kernel.org/stable/c/6ffe44f022c95b1b29c691d2169c5abc046f7580
https://git.kernel.org/stable/c/3cbc242b88c607f55da3d0d0d336b49bf1e20412
reply other threads:[~2026-05-08 14:26 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=2026050849-CVE-2026-43426-eef1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox