bluetooth l2cap

In the Linux kernel’s Bluetooth stack, CVE-2026-31498 is the kind of bug that looks routine at first glance and then turns out to be two problems in one: a resource leak in L2CAP ERTM reconfiguration and a potential infinite loop triggered by a zero packet size. The published fix targets the...

CVE-2026-31498 is a reminder that some of the most consequential kernel bugs are not dramatic buffer overflows or headline-grabbing remote exploits, but state-machine failures and validation gaps buried in long-lived protocol code. In this case, the Linux kernel’s Bluetooth L2CAP layer can be...

Linux has published another Bluetooth kernel fix that looks small on the surface but matters for anyone tracking availability and stability risks in the network stack. CVE-2026-31510 covers a null-pointer dereference in l2cap_sock_ready_cb, where the kernel now checks whether the sk pointer is...

Linux has published CVE-2026-31510 for a Bluetooth L2CAP bug that can crash the kernel when l2cap_sock_ready_cb touches a sk pointer without first checking whether it is NULL. The published record includes a KASAN-backed null-pointer dereference trace and ties the issue to an l2cap_info_timeout...

CVE-2026-31512 is a small-looking Linux kernel flaw with the kind of security significance that only packet-processing code can really deliver. The issue sits in the Bluetooth L2CAP path, where l2cap_ecred_data_rcv() can read the SDU length field before first confirming that the incoming skb...