From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43429: USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts
Date: Fri, 8 May 2026 16:22:38 +0200 [thread overview]
Message-ID: <2026050850-CVE-2026-43429-70a3@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts
The usbtmc driver accepts timeout values specified by the user in an
ioctl command, and uses these timeouts for some usb_bulk_msg() calls.
Since the user can specify arbitrarily long timeouts and
usb_bulk_msg() uses unkillable waits, call usb_bulk_msg_killable()
instead to avoid the possibility of the user hanging a kernel thread
indefinitely.
The Linux kernel CVE team has assigned CVE-2026-43429 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.19 with commit 048c6d88a0214757926f264823829e79154fcd4f and fixed in 5.10.253 with commit e14a0dcdf468c3ad616bb06696c7c64c36e736d8
Issue introduced in 4.19 with commit 048c6d88a0214757926f264823829e79154fcd4f and fixed in 5.15.203 with commit 7fa72c369c23c27d1f64883c1e276af950557fb1
Issue introduced in 4.19 with commit 048c6d88a0214757926f264823829e79154fcd4f and fixed in 6.1.167 with commit 72c0a063489be183cfb99e7050aaef503bdb6449
Issue introduced in 4.19 with commit 048c6d88a0214757926f264823829e79154fcd4f and fixed in 6.6.130 with commit 39bd4097292fd8564cf2cfba9356f8ab11e38d12
Issue introduced in 4.19 with commit 048c6d88a0214757926f264823829e79154fcd4f and fixed in 6.12.78 with commit 0535f84cb94c9d8bcba0a2a5b3fac81b7d97235d
Issue introduced in 4.19 with commit 048c6d88a0214757926f264823829e79154fcd4f and fixed in 6.18.19 with commit 6cb7dc91f057dd8ce44f6caa2995d8e22784ed0a
Issue introduced in 4.19 with commit 048c6d88a0214757926f264823829e79154fcd4f and fixed in 6.19.9 with commit d4f1c45bdff3f393f9ab7e76795901c442b9eb76
Issue introduced in 4.19 with commit 048c6d88a0214757926f264823829e79154fcd4f and fixed in 7.0 with commit 7784caa413a89487dd14dd5c41db8753483b2acb
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-43429
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/class/usbtmc.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/e14a0dcdf468c3ad616bb06696c7c64c36e736d8
https://git.kernel.org/stable/c/7fa72c369c23c27d1f64883c1e276af950557fb1
https://git.kernel.org/stable/c/72c0a063489be183cfb99e7050aaef503bdb6449
https://git.kernel.org/stable/c/39bd4097292fd8564cf2cfba9356f8ab11e38d12
https://git.kernel.org/stable/c/0535f84cb94c9d8bcba0a2a5b3fac81b7d97235d
https://git.kernel.org/stable/c/6cb7dc91f057dd8ce44f6caa2995d8e22784ed0a
https://git.kernel.org/stable/c/d4f1c45bdff3f393f9ab7e76795901c442b9eb76
https://git.kernel.org/stable/c/7784caa413a89487dd14dd5c41db8753483b2acb
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-43429-70a3@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