CVE-2025-40308 — Bluetooth: bcsp: receive data only if registered
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version a4b89a45b12b69bc82c8137346b150a118e02c26version 6.15≥ 6.14.3 and < 6.15≥ 6.13.12 and < 6.14≥ 6.12.24 and < 6.12.58≥ 6.6.88 and < 6.6.117≥ 6.1.135 and < 6.1.159≥ 5.15.181 and < 5.15.197 and 11 more≥ 5.10.237 and < 5.10.247≥ 5.4.293 and < 5.4.302≥ 48effdb7a798232db945503cf3f51e0be8070cea and < 39a7d40314b6288cfa2d13269275e9247a7a055aversion 15543b7bbe7b5f744fdbb44f75b14f81a0117813≥ 366ceff495f902182d42b6f41525c2474caf3f9a and < ca94b2b036c22556c3a66f1b80f490882deef7a6≥ 366ceff495f902182d42b6f41525c2474caf3f9a and < 55c1519fca830f59a10bbf9aa8209c87b06cf7bc≥ 6b7a32fa9bacdebd98c18b2a56994116995ee643 and < b420a4c7f915fc1c94ad1f6ca740acc046d94334≥ 806464634e7fc6b523160defeeddb1ade2a72f81 and < 799cd62cbcc3f12ee04b33ef390ff7d41c37d671≥ 9cf7dccaa7f4c56d2089700e5cb11f85a8d5f6cf and < 8b892dbef3887dbe9afdc7176d1a5fd90e1636aa≥ d71a57a34ab6bbc95dc461158403c02e8ff3f912 and < b65ca9708bfbf47d8b7bd44b7c574bd16798e9c9≥ 45fa7bd82c6178f4fec0ab94891144a043ec5fe8 and < 164586725b47f9d61912e6bf17dbaffeff11710b |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.20%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
10 on the record
- git.kernel.org/stable/c/39a7d40314b6288cfa2d13269275e9247a7a055a
- git.kernel.org/stable/c/b65ca9708bfbf47d8b7bd44b7c574bd16798e9c9
- git.kernel.org/stable/c/8b892dbef3887dbe9afdc7176d1a5fd90e1636aa
- git.kernel.org/stable/c/55c1519fca830f59a10bbf9aa8209c87b06cf7bc
- git.kernel.org/stable/c/ca94b2b036c22556c3a66f1b80f490882deef7a6
- git.kernel.org/stable/c/799cd62cbcc3f12ee04b33ef390ff7d41c37d671
- git.kernel.org/stable/c/b420a4c7f915fc1c94ad1f6ca740acc046d94334
- git.kernel.org/stable/c/164586725b47f9d61912e6bf17dbaffeff11710b
- nvd.nist.gov/vuln/detail/CVE-2025-40308
- github.com/advisories/GHSA-4r3x-4wj9-mxfm
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 13h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 13h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-40308 is "Bluetooth: bcsp: receive data only if registered", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.