CVE-2024-26903
Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security
Severity Score
Exploit Likelihood
Affected Versions
Public Exploits
0Exploited in Wild
-Decision
Descriptions
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.
En el kernel de Linux, se resolvió la siguiente vulnerabilidad: Bluetooth: rfcomm: corrija null-ptr-deref en rfcomm_check_security Durante nuestras pruebas preliminares del proceso de conexión y desconexión en la capa RFCOMM, descubrimos este error. Comparando los paquetes de un proceso normal de conexión y desconexión con el caso de prueba que desencadenó un informe KASAN. Analizamos la causa de este error de la siguiente manera: 1. En los paquetes capturados durante una conexión normal, el host envía un paquete `HCI_CMD` del tipo `Read Encryption Key Size` (código de operación de comando: 0x1408) al controlador para consultar la longitud. de clave de cifrado. Después de recibir este paquete, el controlador responde inmediatamente con un paquete de comando completo (código de evento: 0x0e) para devolver el tamaño de la clave de cifrado. 2. En nuestro caso de prueba fuzz, el tiempo de respuesta del controlador a este paquete se retrasó hasta un punto inesperado: después de que las capas RFCOMM y L2CAP se desconectaran, pero antes de que se desconectara la capa HCI. 3. Después de recibir la respuesta del tamaño de la clave de cifrado en el momento descrito en el punto 2, el host aún llamó a la función rfcomm_check_security. Sin embargo, en ese momento `struct l2cap_conn *conn = l2cap_pi(sk)->chan->conn;` ya se había lanzado, y cuando se ejecutó la función `return hci_conn_security(conn->hcon, d->sec_level, auth_type, d ->out);`, específicamente al acceder a `conn->hcon`, ocurrió un error null-ptr-deref. Para corregir este error, verifique si `sk->sk_state` está BT_CLOSED antes de llamar a rfcomm_recv_frame en rfcomm_process_rx.
CVSS Scores
SSVC
- Decision:Track
Timeline
- 2024-02-19 CVE Reserved
- 2024-04-17 CVE Published
- 2024-04-30 EPSS Updated
- 2024-12-19 CVE Updated
- ---------- Exploited in Wild
- ---------- KEV Due Date
- ---------- First Exploit
CWE
- CWE-476: NULL Pointer Dereference
CAPEC
References (12)
URL | Tag | Source |
---|---|---|
https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html | ||
https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html |
URL | Date | SRC |
---|
URL | Date | SRC |
---|---|---|
https://access.redhat.com/security/cve/CVE-2024-26903 | 2024-11-12 | |
https://bugzilla.redhat.com/show_bug.cgi?id=2275641 | 2024-11-12 |
Affected Vendors, Products, and Versions
Vendor | Product | Version | Other | Status | ||||||
---|---|---|---|---|---|---|---|---|---|---|
Vendor | Product | Version | Other | Status | <-- --> | Vendor | Product | Version | Other | Status |
Linux Search vendor "Linux" | Linux Kernel Search vendor "Linux" for product "Linux Kernel" | < 4.19.311 Search vendor "Linux" for product "Linux Kernel" and version " < 4.19.311" | en |
Affected
| ||||||
Linux Search vendor "Linux" | Linux Kernel Search vendor "Linux" for product "Linux Kernel" | < 5.4.273 Search vendor "Linux" for product "Linux Kernel" and version " < 5.4.273" | en |
Affected
| ||||||
Linux Search vendor "Linux" | Linux Kernel Search vendor "Linux" for product "Linux Kernel" | < 5.10.214 Search vendor "Linux" for product "Linux Kernel" and version " < 5.10.214" | en |
Affected
| ||||||
Linux Search vendor "Linux" | Linux Kernel Search vendor "Linux" for product "Linux Kernel" | < 5.15.153 Search vendor "Linux" for product "Linux Kernel" and version " < 5.15.153" | en |
Affected
| ||||||
Linux Search vendor "Linux" | Linux Kernel Search vendor "Linux" for product "Linux Kernel" | < 6.1.83 Search vendor "Linux" for product "Linux Kernel" and version " < 6.1.83" | en |
Affected
| ||||||
Linux Search vendor "Linux" | Linux Kernel Search vendor "Linux" for product "Linux Kernel" | < 6.6.23 Search vendor "Linux" for product "Linux Kernel" and version " < 6.6.23" | en |
Affected
| ||||||
Linux Search vendor "Linux" | Linux Kernel Search vendor "Linux" for product "Linux Kernel" | < 6.7.11 Search vendor "Linux" for product "Linux Kernel" and version " < 6.7.11" | en |
Affected
| ||||||
Linux Search vendor "Linux" | Linux Kernel Search vendor "Linux" for product "Linux Kernel" | < 6.8 Search vendor "Linux" for product "Linux Kernel" and version " < 6.8" | en |
Affected
|