From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43432: usb: xhci: Fix memory leak in xhci_disable_slot()
Date: Fri, 8 May 2026 16:22:41 +0200 [thread overview]
Message-ID: <2026050851-CVE-2026-43432-18dd@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
usb: xhci: Fix memory leak in xhci_disable_slot()
xhci_alloc_command() allocates a command structure and, when the
second argument is true, also allocates a completion structure.
Currently, the error handling path in xhci_disable_slot() only frees
the command structure using kfree(), causing the completion structure
to leak.
Use xhci_free_command() instead of kfree(). xhci_free_command() correctly
frees both the command structure and the associated completion structure.
Since the command structure is allocated with zero-initialization,
command->in_ctx is NULL and will not be erroneously freed by
xhci_free_command().
This bug was found using an experimental static analysis tool we are
developing. The tool is based on the LLVM framework and is specifically
designed to detect memory management issues. It is currently under
active development and not yet publicly available, but we plan to
open-source it after our research is published.
The bug was originally detected on v6.13-rc1 using our static analysis
tool, and we have verified that the issue persists in the latest mainline
kernel.
We performed build testing on x86_64 with allyesconfig using GCC=11.4.0.
Since triggering these error paths in xhci_disable_slot() requires specific
hardware conditions or abnormal state, we were unable to construct a test
case to reliably trigger these specific error paths at runtime.
The Linux kernel CVE team has assigned CVE-2026-43432 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10.85 with commit fee8be5bde562d4f5f9a100ca80c6d7072ed34c8 and fixed in 5.10.253 with commit 1e800e26d54ccf2ddf2ea6d6cbe021c804d8aa62
Issue introduced in 5.15.8 with commit 02d5a2a48bb44e7404b794df87e57588b2fd604e and fixed in 5.15.203 with commit 6288baf0c8c4dcfbf206773aede9c1f2269cec28
Issue introduced in 5.16 with commit 7faac1953ed1f658f719cdf7bb7303fa5eef822c and fixed in 6.1.167 with commit 46aea90763832cd6e9b0c2e1c00e6a9512156d4b
Issue introduced in 5.16 with commit 7faac1953ed1f658f719cdf7bb7303fa5eef822c and fixed in 6.6.130 with commit 2e2baa8fb5aa4d080cbfeb84c51eff797529f413
Issue introduced in 5.16 with commit 7faac1953ed1f658f719cdf7bb7303fa5eef822c and fixed in 6.12.78 with commit 807e4fb5140c73eb5dba1e399a990db5c1f3cdf8
Issue introduced in 5.16 with commit 7faac1953ed1f658f719cdf7bb7303fa5eef822c and fixed in 6.18.19 with commit c65f1b840ab8ce72ba68f1b63bab7960f8fdfa89
Issue introduced in 5.16 with commit 7faac1953ed1f658f719cdf7bb7303fa5eef822c and fixed in 6.19.9 with commit 078b446efc0f5e496c31bccb72b98af979963a83
Issue introduced in 5.16 with commit 7faac1953ed1f658f719cdf7bb7303fa5eef822c and fixed in 7.0 with commit c1c8550e70401159184130a1afc6261db01fc0ce
Issue introduced in 4.19.221 with commit cc7c2818c71ebace207df40cc586c8c74e3d1a59
Issue introduced in 5.4.165 with commit ec0cddcc2454ab08193beb473978f8f8889b7e24
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-43432
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/host/xhci.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/1e800e26d54ccf2ddf2ea6d6cbe021c804d8aa62
https://git.kernel.org/stable/c/6288baf0c8c4dcfbf206773aede9c1f2269cec28
https://git.kernel.org/stable/c/46aea90763832cd6e9b0c2e1c00e6a9512156d4b
https://git.kernel.org/stable/c/2e2baa8fb5aa4d080cbfeb84c51eff797529f413
https://git.kernel.org/stable/c/807e4fb5140c73eb5dba1e399a990db5c1f3cdf8
https://git.kernel.org/stable/c/c65f1b840ab8ce72ba68f1b63bab7960f8fdfa89
https://git.kernel.org/stable/c/078b446efc0f5e496c31bccb72b98af979963a83
https://git.kernel.org/stable/c/c1c8550e70401159184130a1afc6261db01fc0ce
reply other threads:[~2026-05-08 14:25 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=2026050851-CVE-2026-43432-18dd@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