From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-26801: Bluetooth: Avoid potential use-after-free in hci_error_reset
Date: Thu, 4 Apr 2024 10:23:18 +0200 [thread overview]
Message-ID: <2024040403-CVE-2024-26801-da9f@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: Avoid potential use-after-free in hci_error_reset
While handling the HCI_EV_HARDWARE_ERROR event, if the underlying
BT controller is not responding, the GPIO reset mechanism would
free the hci_dev and lead to a use-after-free in hci_error_reset.
Here's the call trace observed on a ChromeOS device with Intel AX201:
queue_work_on+0x3e/0x6c
__hci_cmd_sync_sk+0x2ee/0x4c0 [bluetooth <HASH:3b4a6>]
? init_wait_entry+0x31/0x31
__hci_cmd_sync+0x16/0x20 [bluetooth <HASH:3b4a 6>]
hci_error_reset+0x4f/0xa4 [bluetooth <HASH:3b4a 6>]
process_one_work+0x1d8/0x33f
worker_thread+0x21b/0x373
kthread+0x13a/0x152
? pr_cont_work+0x54/0x54
? kthread_blkcg+0x31/0x31
ret_from_fork+0x1f/0x30
This patch holds the reference count on the hci_dev while processing
a HCI_EV_HARDWARE_ERROR event to avoid potential crash.
The Linux kernel CVE team has assigned CVE-2024-26801 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.0 with commit c7741d16a57c and fixed in 4.19.309 with commit e0b278650f07
Issue introduced in 4.0 with commit c7741d16a57c and fixed in 5.4.271 with commit 98fb98fd37e4
Issue introduced in 4.0 with commit c7741d16a57c and fixed in 5.10.212 with commit 6dd0a9dfa99f
Issue introduced in 4.0 with commit c7741d16a57c and fixed in 5.15.151 with commit da4569d450b1
Issue introduced in 4.0 with commit c7741d16a57c and fixed in 6.1.81 with commit 45085686b955
Issue introduced in 4.0 with commit c7741d16a57c and fixed in 6.6.21 with commit 2ab9a19d896f
Issue introduced in 4.0 with commit c7741d16a57c and fixed in 6.7.9 with commit dd594cdc24f2
Issue introduced in 4.0 with commit c7741d16a57c and fixed in 6.8 with commit 2449007d3f73
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-2024-26801
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:
net/bluetooth/hci_core.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/e0b278650f07acf2e0932149183458468a731c03
https://git.kernel.org/stable/c/98fb98fd37e42fd4ce13ff657ea64503e24b6090
https://git.kernel.org/stable/c/6dd0a9dfa99f8990a08eb8fdd8e79bee31c7d8e2
https://git.kernel.org/stable/c/da4569d450b193e39e87119fd316c0291b585d14
https://git.kernel.org/stable/c/45085686b9559bfbe3a4f41d3d695a520668f5e1
https://git.kernel.org/stable/c/2ab9a19d896f5a0dd386e1f001c5309bc35f433b
https://git.kernel.org/stable/c/dd594cdc24f2e48dab441732e6dfcafd6b0711d1
https://git.kernel.org/stable/c/2449007d3f73b2842c9734f45f0aadb522daf592
reply other threads:[~2024-04-04 8:24 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=2024040403-CVE-2024-26801-da9f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@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;
as well as URLs for NNTP newsgroup(s).