[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022606-CVE-2022-49138-a241@gregkh>
Date: Wed, 26 Feb 2025 02:55:43 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49138: Bluetooth: hci_event: Ignore multiple conn complete events
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_event: Ignore multiple conn complete events
When one of the three connection complete events is received multiple
times for the same handle, the device is registered multiple times which
leads to memory corruptions. Therefore, consequent events for a single
connection are ignored.
The conn->state can hold different values, therefore HCI_CONN_HANDLE_UNSET
is introduced to identify new connections. To make sure the events do not
contain this or another invalid handle HCI_CONN_HANDLE_MAX and checks
are introduced.
Buglink: https://bugzilla.kernel.org/show_bug.cgi?id=215497
The Linux kernel CVE team has assigned CVE-2022-49138 to this issue.
Affected and fixed versions
===========================
Fixed in 5.17.3 with commit aa1ca580e3ffe62a2c5ea1c095b609b2943c5269
Fixed in 5.18 with commit d5ebaa7c5f6f688959e8d40840b2249ede63b8ed
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-49138
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:
include/net/bluetooth/hci_core.h
net/bluetooth/hci_conn.c
net/bluetooth/hci_event.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/aa1ca580e3ffe62a2c5ea1c095b609b2943c5269
https://git.kernel.org/stable/c/d5ebaa7c5f6f688959e8d40840b2249ede63b8ed
Powered by blists - more mailing lists