CVE-2024-26903 Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security

Medium 5.5 Published Updated

A race condition in the Linux kernel Bluetooth stack causes a null pointer dereference, leading to a system crash.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2024-26903?

CVE-2024-26903 is a medium-severity vulnerability in Linux kernel, published on 17 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Weakness: CWE-476

Which versions are affected by CVE-2024-26903?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2024-26903?

Apply the vendor's patch.

Is CVE-2024-26903 being exploited?

There is no known exploitation of CVE-2024-26903 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as AZL-40088, BELL-CVE-2024-26903, DEBIAN-CVE-2024-26903, GHSA-w69g-9g23-pfwc, UBUNTU-CVE-2024-26903.

Is CVE-2024-26903 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free