CVE-2024-26903Medium· 5.5▾ SunlitIn 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 t…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 30.3 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Oct 15.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
Last analysed / modified upstream
0.3%
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:
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.
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.
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.
linux_kernel < 4.19.311linux_kernel >= 4.20, < 5.4.273linux_kernel >= 5.5, < 5.10.214linux_kernel >= 5.11, < 5.15.153linux_kernel >= 5.16, < 6.1.83linux_kernel >= 6.2, < 6.6.23linux_kernel >= 6.7, < 6.7.11Upgrade past the affected range:
linux_kernel 6.7.11Connected by shared product, vendor, weakness, or advisory.
CVE-2021-3739High· 7.1A NULL pointer dereference flaw was found in the btrfs_rm_device function in fs/btrfs/volumes.c in the Linux Kernel, where triggering the bug requires ‘CAP_SYS_ADMIN’
CVE-2022-3104Medium· 5.5An issue was discovered in the Linux kernel through 5.16-rc6
CVE-2022-3115Medium· 5.5An issue was discovered in the Linux kernel through 5.16-rc6
CVE-2022-3621Medium· 4.3A vulnerability was found in Linux Kernel
CVE-2022-2153Medium· 5.5A flaw was found in the Linux kernel’s KVM when attempting to set a SynIC IRQ
CVE-2022-1852Medium· 5.5A NULL pointer dereference flaw was found in the Linux kernel’s KVM module, which can lead to a denial of service in the x86_emulate_insn in arch/x86/kvm/emulate.c