CVE-2024-26903
"Bluetooth Cisco - Null Pointer Dereference"
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security During our fuzz testing of the connection and disconnection process at the RFCOMM layer, we discovered this bug. By comparing the packets from a normal connection and disconnection process with the testcase that triggered a KASAN report. We analyzed the cause of this bug as follows: 1. In the packets captured during a normal connection, the host sends a `Read Encryption Key Size` type of `HCI_CMD` packet (Command Opcode: 0x1408) to the controller to inquire the length of encryption key.After receiving this packet, the controller immediately replies with a Command Completepacket (Event Code: 0x0e) to return the Encryption Key Size. 2. In our fuzz test case, the timing of the controller's response to this packet was delayed to an unexpected point: after the RFCOMM and L2CAP layers had disconnected but before the HCI layer had disconnected. 3. After receiving the Encryption Key Size Response at the time described in point 2, the host still called the rfcomm_check_security function. However, by this time `struct l2cap_conn *conn = l2cap_pi(sk)->chan->conn;` had already been released, and when the function executed `return hci_conn_security(conn->hcon, d->sec_level, auth_type, d->out);`, specifically when accessing `conn->hcon`, a null-ptr-deref error occurred. To fix this bug, check if `sk->sk_state` is BT_CLOSED before calling rfcomm_recv_frame in rfcomm_process_rx.
INFO
Published Date :
April 17, 2024, 11:15 a.m.
Last Modified :
June 27, 2024, 12:15 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-26903
.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-26903
vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-26903
vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 27, 2024
Action Type Old Value New Value Added Reference kernel.org https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html [No types assigned] -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 25, 2024
Action Type Old Value New Value Added Reference kernel.org https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html [No types assigned] -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 29, 2024
Action Type Old Value New Value -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Apr. 29, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Changed Reference Type https://git.kernel.org/stable/c/2535b848fa0f42ddff3e5255cf5e742c9b77bb26 No Types Assigned https://git.kernel.org/stable/c/2535b848fa0f42ddff3e5255cf5e742c9b77bb26 Patch Changed Reference Type https://git.kernel.org/stable/c/369f419c097e82407dd429a202cde9a73d3ae29b No Types Assigned https://git.kernel.org/stable/c/369f419c097e82407dd429a202cde9a73d3ae29b Patch Changed Reference Type https://git.kernel.org/stable/c/3ead59bafad05f2967ae2438c0528d53244cfde5 No Types Assigned https://git.kernel.org/stable/c/3ead59bafad05f2967ae2438c0528d53244cfde5 Patch Changed Reference Type https://git.kernel.org/stable/c/567c0411dc3b424fc7bd1e6109726d7ba32d4f73 No Types Assigned https://git.kernel.org/stable/c/567c0411dc3b424fc7bd1e6109726d7ba32d4f73 Patch Changed Reference Type https://git.kernel.org/stable/c/5f369efd9d963c1f711a06c9b8baf9f5ce616d85 No Types Assigned https://git.kernel.org/stable/c/5f369efd9d963c1f711a06c9b8baf9f5ce616d85 Patch Changed Reference Type https://git.kernel.org/stable/c/5f9fe302dd3a9bbc50f4888464c1773f45166bfd No Types Assigned https://git.kernel.org/stable/c/5f9fe302dd3a9bbc50f4888464c1773f45166bfd Patch Changed Reference Type https://git.kernel.org/stable/c/81d7d920a22fd58ef9aedb1bd0a68ee32bd23e96 No Types Assigned https://git.kernel.org/stable/c/81d7d920a22fd58ef9aedb1bd0a68ee32bd23e96 Patch Changed Reference Type https://git.kernel.org/stable/c/8d1753973f598531baaa2c1033cf7f7b5bb004b0 No Types Assigned https://git.kernel.org/stable/c/8d1753973f598531baaa2c1033cf7f7b5bb004b0 Patch Added CWE NIST CWE-476 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 4.19.311 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.20 up to (excluding) 5.4.273 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.214 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.153 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.83 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.23 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.7.11 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Apr. 17, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security During our fuzz testing of the connection and disconnection process at the RFCOMM layer, we discovered this bug. By comparing the packets from a normal connection and disconnection process with the testcase that triggered a KASAN report. We analyzed the cause of this bug as follows: 1. In the packets captured during a normal connection, the host sends a `Read Encryption Key Size` type of `HCI_CMD` packet (Command Opcode: 0x1408) to the controller to inquire the length of encryption key.After receiving this packet, the controller immediately replies with a Command Completepacket (Event Code: 0x0e) to return the Encryption Key Size. 2. In our fuzz test case, the timing of the controller's response to this packet was delayed to an unexpected point: after the RFCOMM and L2CAP layers had disconnected but before the HCI layer had disconnected. 3. After receiving the Encryption Key Size Response at the time described in point 2, the host still called the rfcomm_check_security function. However, by this time `struct l2cap_conn *conn = l2cap_pi(sk)->chan->conn;` had already been released, and when the function executed `return hci_conn_security(conn->hcon, d->sec_level, auth_type, d->out);`, specifically when accessing `conn->hcon`, a null-ptr-deref error occurred. To fix this bug, check if `sk->sk_state` is BT_CLOSED before calling rfcomm_recv_frame in rfcomm_process_rx. Added Reference kernel.org https://git.kernel.org/stable/c/369f419c097e82407dd429a202cde9a73d3ae29b [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/5f369efd9d963c1f711a06c9b8baf9f5ce616d85 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/81d7d920a22fd58ef9aedb1bd0a68ee32bd23e96 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/8d1753973f598531baaa2c1033cf7f7b5bb004b0 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/567c0411dc3b424fc7bd1e6109726d7ba32d4f73 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/3ead59bafad05f2967ae2438c0528d53244cfde5 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/5f9fe302dd3a9bbc50f4888464c1773f45166bfd [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/2535b848fa0f42ddff3e5255cf5e742c9b77bb26 [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-26903
is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-26903
weaknesses.