Package: linux-image-6.1.0-56-amd64 Version: 6.1.192-2 Severity: important Tags: regression bookworm
Dear Debian Kernel Team, After upgrading the kernel from 6.1.190-1 to 6.1.192-2 on November 16, 2026, I experienced repeated kernel oops events related to the Bluetooth subsystem immediately after the next system boot. The Bluetooth daemon repeatedly crashes and is restarted via D-Bus activation requested by WirePlumber. The Bluetooth tray icon continuously disappears and reappears, interrupting normal desktop interaction and keyboard input. Both kernel and system logs grow continuously. System information: - Distribution: LMDE 6 (Faye), based on Debian 12 (Bookworm) - Architecture: amd64 - Desktop environment: Cinnamon - Laptop: Lenovo V15-IIL (82C5) - BIOS: DKCN55WW (2022-05-24) - Bluetooth adapter: Realtek USB Bluetooth Radio (0bda:c02f) - Wi-Fi adapter: Realtek RTL8822CE - BlueZ version: 5.66 Kernel versions tested: - linux-image-6.1.0-54-amd64 (6.1.190-1): WORKING - linux-image-6.1.0-56-amd64 (6.1.192-2): BROKEN The first kernel oops occurs shortly after boot, while the kernel is still untainted. Relevant kernel log: list_del corruption, ffff88ec430af0c0->prev is LIST_POISON2 (dead000000000122) kernel BUG at lib/list_debug.c:56! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI Comm: bluetoothd Not tainted 6.1.0-56-amd64 #1 Debian 6.1.192-2 Call Trace: hci_chan_del+0x18/0x90 [bluetooth] l2cap_chan_put+0x106/0x130 [bluetooth] l2cap_sock_release+0xca/0x100 [bluetooth] __sock_release+0x3d/0xb0 sock_close+0x11/0x20 __fput+0x93/0x250 task_work_run+0x56/0x90 Steps to reproduce: 1. Upgrade the kernel to version 6.1.192-2. 2. Reboot with Bluetooth enabled. 3. Observe repeated Bluetooth daemon crashes and kernel oops events. Expected behaviour: Bluetooth should operate normally without kernel oops events. Actual behaviour: The Bluetooth subsystem enters a continuous crash and restart loop. More than 100 kernel oops events were recorded within approximately 16 minutes. Workaround: Booting the previous kernel (6.1.190-1) completely resolves the problem. Bluetooth works normally without any changes to the hardware or Bluetooth configuration. This appears to be a regression introduced between kernel versions 6.1.190 and 6.1.192, possibly related to Bluetooth L2CAP channel cleanup. Please find the relevant kernel log attached. Thank you for your assistance. Best regards, Peter

