CVE-2024-50077

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: ISO: Fix multiple init when debugfs is disabled<br /> <br /> If bt_debugfs is not created successfully, which happens if either<br /> CONFIG_DEBUG_FS or CONFIG_DEBUG_FS_ALLOW_ALL is unset, then iso_init()<br /> returns early and does not set iso_inited to true. This means that a<br /> subsequent call to iso_init() will result in duplicate calls to<br /> proto_register(), bt_sock_register(), etc.<br /> <br /> With CONFIG_LIST_HARDENED and CONFIG_BUG_ON_DATA_CORRUPTION enabled, the<br /> duplicate call to proto_register() triggers this BUG():<br /> <br /> list_add double add: new=ffffffffc0b280d0, prev=ffffffffbab56250,<br /> next=ffffffffc0b280d0.<br /> ------------[ cut here ]------------<br /> kernel BUG at lib/list_debug.c:35!<br /> Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI<br /> CPU: 2 PID: 887 Comm: bluetoothd Not tainted 6.10.11-1-ao-desktop #1<br /> RIP: 0010:__list_add_valid_or_report+0x9a/0xa0<br /> ...<br /> __list_add_valid_or_report+0x9a/0xa0<br /> proto_register+0x2b5/0x340<br /> iso_init+0x23/0x150 [bluetooth]<br /> set_iso_socket_func+0x68/0x1b0 [bluetooth]<br /> kmem_cache_free+0x308/0x330<br /> hci_sock_sendmsg+0x990/0x9e0 [bluetooth]<br /> __sock_sendmsg+0x7b/0x80<br /> sock_write_iter+0x9a/0x110<br /> do_iter_readv_writev+0x11d/0x220<br /> vfs_writev+0x180/0x3e0<br /> do_writev+0xca/0x100<br /> ...<br /> <br /> This change removes the early return. The check for iso_debugfs being<br /> NULL was unnecessary, it is always NULL when iso_inited is false.