CVE-2025-40308

Bluetooth: bcsp: receive data only if registered

N/A
Published: December 8, 2025 at 12:46 AM UTC
Updated: October 14, 2026 at 10:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: bcsp: receive data only if registered Currently, bcsp_recv() can be called even when the BCSP protocol has not been registered. This leads to a NULL pointer dereference, as shown in the following stack trace: KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f] RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590 Call Trace: <TASK> hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627 tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290 tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f To prevent this, ensure that the HCI_UART_REGISTERED flag is set before processing received data. If the protocol is not registered, return -EUNATCH.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10.237 ≤ v < 5.10.2475.15.181 ≤ v < 5.15.1975.4.293 ≤ v < 5.4.3026.1.135 ≤ v < 6.1.1596.12.24 ≤ v < 6.12.586.13.12 ≤ v < 6.146.14.3 ≤ v < 6.156.6.88 ≤ v < 6.6.11715543b7bbe7b5f744fdbb44f75b14f81a0117813366ceff495f902182d42b6f41525c2474caf3f9a45fa7bd82c6178f4fec0ab94891144a043ec5fe848effdb7a798232db945503cf3f51e0be8070cea5.10.2375.15.1815.4.2936.1.1356.12.246.13.126.14.36.156.6.886b7a32fa9bacdebd98c18b2a56994116995ee643806464634e7fc6b523160defeeddb1ade2a72f819cf7dccaa7f4c56d2089700e5cb11f85a8d5f6cfa4b89a45b12b69bc82c8137346b150a118e02c26d71a57a34ab6bbc95dc461158403c02e8ff3f912
Vendor states this is fixed in 164586725b47f9d61912e6bf17dbaffeff11710b (fixed)
Vendor states this is fixed in 39a7d40314b6288cfa2d13269275e9247a7a055a (fixed)
Vendor states this is fixed in 55c1519fca830f59a10bbf9aa8209c87b06cf7bc (fixed)
Vendor states this is fixed in 799cd62cbcc3f12ee04b33ef390ff7d41c37d671 (fixed)
Vendor states this is fixed in 8b892dbef3887dbe9afdc7176d1a5fd90e1636aa (fixed)
Vendor states this is fixed in b420a4c7f915fc1c94ad1f6ca740acc046d94334 (fixed)
Vendor states this is fixed in b65ca9708bfbf47d8b7bd44b7c574bd16798e9c9 (fixed)
Vendor states this is fixed in ca94b2b036c22556c3a66f1b80f490882deef7a6 (fixed)
Vendor states this is fixed in 5.10.247 (unaffected)
Vendor states this is fixed in 5.15.197 (unaffected)
Vendor states this is fixed in 5.4.302 (unaffected)
Vendor states this is fixed in 6.1.159 (unaffected)
Vendor states this is fixed in 6.12.58 (unaffected)
Affected range stops below 6.14, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.15 (unaffected)
Vendor states this is fixed in 6.17.8 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.117 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card