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
Metrics
Affected Vendors & Products
References
History
Thu, 01 May 2025 03:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-672 |
Thu, 27 Feb 2025 13:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Wed, 26 Feb 2025 02:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
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 | |
Title | Bluetooth: hci_event: Ignore multiple conn complete events | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-02-26T01:55:10.632Z
Updated: 2025-02-26T01:55:10.632Z
Reserved: 2025-02-26T01:49:39.268Z
Link: CVE-2022-49138

No data.

Status : Received
Published: 2025-02-26T07:00:51.047
Modified: 2025-02-26T07:00:51.047
Link: CVE-2022-49138
