From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89737: usb: typec: thunderbolt: Disable work before freeing tbt on remove
Date: Fri, 11 Sep 2026 21:47:06 +0200 [thread overview]
Message-ID: <2026091104-CVE-2026-89737-7101@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
usb: typec: thunderbolt: Disable work before freeing tbt on remove
tbt_altmode_remove() drops the plug and cable references without
draining tbt->work. The work function dereferences those references,
and can also requeue itself in its error path. The VDM callbacks can
queue the same work item.
Disable and drain tbt->work before dropping the references. This waits
for an existing invocation and prevents subsequent schedule_work()
calls from queueing it during teardown.
This issue was found by an in-house static analysis tool and confirmed
by manual code review.
The Linux kernel CVE team has assigned CVE-2026-89737 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.14 with commit 100e257386595b3f1865ca8a991e2ba74f9701ff and fixed in 6.18.50 with commit ebb840d982a612261cfc8a7687735a140c6c7024
Issue introduced in 6.14 with commit 100e257386595b3f1865ca8a991e2ba74f9701ff and fixed in 7.2.4 with commit 0a25484fe22f621e151367a59a82330a22ac80bc
Issue introduced in 6.14 with commit 100e257386595b3f1865ca8a991e2ba74f9701ff and fixed in 7.3-rc1 with commit 92090f6ff2acc81e9dd99881dcfb4f8c1bdaabd3
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-89737
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/typec/altmodes/thunderbolt.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/ebb840d982a612261cfc8a7687735a140c6c7024
https://git.kernel.org/stable/c/0a25484fe22f621e151367a59a82330a22ac80bc
https://git.kernel.org/stable/c/92090f6ff2acc81e9dd99881dcfb4f8c1bdaabd3
reply other threads:[~2026-09-11 20:05 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=2026091104-CVE-2026-89737-7101@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