From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64144: Bluetooth: btmtk: fix urb->setup_packet leak in error paths
Date: Sun, 19 Jul 2026 17:40:06 +0200 [thread overview]
Message-ID: <2026071930-CVE-2026-64144-5963@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btmtk: fix urb->setup_packet leak in error paths
The setup_packet of control urb is not freed if usb_submit_urb fails or
the submitted urb is killed. Add free in these two paths.
The Linux kernel CVE team has assigned CVE-2026-64144 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.3 with commit a1c49c434e15050b5dafe3b6f5cc732d4f02d657 and fixed in 6.6.142 with commit 2a1905730e0c771b999906a7b509722f795563c6
Issue introduced in 5.3 with commit a1c49c434e15050b5dafe3b6f5cc732d4f02d657 and fixed in 6.12.92 with commit 68c027c2003b0a8a1439d0301c59c6fd1eb3b844
Issue introduced in 5.3 with commit a1c49c434e15050b5dafe3b6f5cc732d4f02d657 and fixed in 6.18.34 with commit a0f5268c77eb73f84ba7c210ddfc54b1c73ff80c
Issue introduced in 5.3 with commit a1c49c434e15050b5dafe3b6f5cc732d4f02d657 and fixed in 7.0.11 with commit 0d2572bafea33c7cd1d77c6a25f25ff31a432482
Issue introduced in 5.3 with commit a1c49c434e15050b5dafe3b6f5cc732d4f02d657 and fixed in 7.1 with commit dd1dda6b8d6e1f4376a5b3055a04f0ecbdb4d6bd
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-64144
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/bluetooth/btmtk.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/2a1905730e0c771b999906a7b509722f795563c6
https://git.kernel.org/stable/c/68c027c2003b0a8a1439d0301c59c6fd1eb3b844
https://git.kernel.org/stable/c/a0f5268c77eb73f84ba7c210ddfc54b1c73ff80c
https://git.kernel.org/stable/c/0d2572bafea33c7cd1d77c6a25f25ff31a432482
https://git.kernel.org/stable/c/dd1dda6b8d6e1f4376a5b3055a04f0ecbdb4d6bd
reply other threads:[~2026-07-19 15:45 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=2026071930-CVE-2026-64144-5963@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