CVE-2026-97408: Bluetooth: L2CAP: validate connectionless PSM length
Bluetooth: L2CAP: validate connectionless PSM length
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.158.1-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.190-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.14-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1
Event History
Frequently Asked Questions
What does an attacker need to send to trigger the flawed parsing path?
They need to deliver a malformed connectionless L2CAP frame whose payload is zero or one byte long. The vulnerable parser attempts to read the required two-byte PSM despite the payload being too short.
Which systems are realistically exposed?
Systems using the Linux kernel Bluetooth L2CAP receive path are potentially exposed when they can receive connectionless L2CAP frames. The provided data does not identify specific kernel versions, Bluetooth hardware, or configuration requirements.
What changes after applying the fix?
The kernel rejects connectionless frames that are too short to contain the two-byte PSM before attempting to read it. Valid connectionless frames are preserved; only structurally incomplete packets are dropped.
Can this condition be detected from the provided information?
A reproducer can inject a one-byte connectionless payload through a VHCI-backed QEMU setup and reach the unchecked read on an affected kernel. The provided data does not specify a log message, crash signature, or runtime indicator for identifying prior exploitation.