Vulnerability · Published Apr 17, 2024 · Assigned by Linux

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

Medium 5.5

In plain English

A medium-severity null pointer dereference in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 20% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.5Medium
Exploit odds (30 days)0.3%top 79.5% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.82-1DEBIAN-CVE-2024-26903
Debian:13linux6.7.12-1DEBIAN-CVE-2024-26903
Debian:14linux6.7.12-1DEBIAN-CVE-2024-26903
Ubuntu:22.04:LTSlinux5.15.0-112.122UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-aws5.15.0-1063.69UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-azure5.15.0-1066.75UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1067.76.1UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-gcp5.15.0-1062.70UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-gke5.15.0-1060.66UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1046.53UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-ibm5.15.0-1056.59UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1058.64UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-kvm5.15.0-1060.65UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-110.120UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1058.59UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1026.26UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1015.15UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-oracle5.15.0-1061.67UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-raspi5.15.0-1058.61UBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2024-26903
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1030.34UBUNTU-CVE-2024-26903

Affected products (as reported)

VendorProductVersions
Linux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 369f419c097e82407dd429a202cde9a73d3ae29b1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 5f369efd9d963c1f711a06c9b8baf9f5ce616d851da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 81d7d920a22fd58ef9aedb1bd0a68ee32bd23e961da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 8d1753973f598531baaa2c1033cf7f7b5bb004b01da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 567c0411dc3b424fc7bd1e6109726d7ba32d4f731da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 3ead59bafad05f2967ae2438c0528d53244cfde51da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 5f9fe302dd3a9bbc50f4888464c1773f45166bfd1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 2535b848fa0f42ddff3e5255cf5e742c9b77bb26
Linux Linux 2.6.12

Weakness: CWE-476 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

References