Linux kernel CVE announcements
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43430: usb: yurex: fix race in probe
Date: Fri,  8 May 2026 16:22:39 +0200	[thread overview]
Message-ID: <2026050850-CVE-2026-43430-a1d8@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

usb: yurex: fix race in probe

The bbu member of the descriptor must be set to the value
standing for uninitialized values before the URB whose
completion handler sets bbu is submitted. Otherwise there is
a window during which probing can overwrite already retrieved
data.

The Linux kernel CVE team has assigned CVE-2026-43430 to this issue.


Affected and fixed versions
===========================

	Fixed in 5.10.253 with commit a7934d7202a39c3160aa30521c382c7b744ae4a2
	Fixed in 5.15.203 with commit a8b3b3d730acea1640bc89465f2832cf06a1e13a
	Fixed in 6.1.167 with commit 687d26d43a5aaf44323ce7d601cf242bb87e9559
	Fixed in 6.6.130 with commit 939e3d17b843b0bae70467fef4481069d73c8520
	Fixed in 6.12.78 with commit 3cec135415a89723e2d38e1c8cc5098203355965
	Fixed in 6.18.19 with commit a41d3d9202e951995cfac6248c565423079c71fa
	Fixed in 6.19.9 with commit af83e92c329f11139d5eea2b5b7b83c26c3f67e7
	Fixed in 7.0 with commit 7a875c09899ba0404844abfd8f0d54cdc481c151

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-43430
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/misc/yurex.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/a7934d7202a39c3160aa30521c382c7b744ae4a2
	https://git.kernel.org/stable/c/a8b3b3d730acea1640bc89465f2832cf06a1e13a
	https://git.kernel.org/stable/c/687d26d43a5aaf44323ce7d601cf242bb87e9559
	https://git.kernel.org/stable/c/939e3d17b843b0bae70467fef4481069d73c8520
	https://git.kernel.org/stable/c/3cec135415a89723e2d38e1c8cc5098203355965
	https://git.kernel.org/stable/c/a41d3d9202e951995cfac6248c565423079c71fa
	https://git.kernel.org/stable/c/af83e92c329f11139d5eea2b5b7b83c26c3f67e7
	https://git.kernel.org/stable/c/7a875c09899ba0404844abfd8f0d54cdc481c151

                 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=2026050850-CVE-2026-43430-a1d8@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