blob: 4cf1d555a09f9e764c50877ae423e04064e2c425 [file] [log] [blame]
From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2022-49136: Bluetooth: hci_sync: Fix queuing commands when HCI_UNREGISTER is set
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_sync: Fix queuing commands when HCI_UNREGISTER is set
hci_cmd_sync_queue shall return an error if HCI_UNREGISTER flag has
been set as that means hci_unregister_dev has been called so it will
likely cause a uaf after the timeout as the hdev will be freed.
The Linux kernel CVE team has assigned CVE-2022-49136 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.17 with commit 6a98e3836fa2077b169f10a35c2ca9952d53f987 and fixed in 5.17.3 with commit 1c69ef84a808676cceb69210addf5df45b741323
Issue introduced in 5.17 with commit 6a98e3836fa2077b169f10a35c2ca9952d53f987 and fixed in 5.18 with commit 0b94f2651f56b9e4aa5f012b0d7eb57308c773cf
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-2022-49136
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_sync.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/1c69ef84a808676cceb69210addf5df45b741323
https://git.kernel.org/stable/c/0b94f2651f56b9e4aa5f012b0d7eb57308c773cf