Answer in brief
CVE-2024-50077 records a High severity (CVSS 7.8) vulnerability in Bluetooth: ISO: Fix multiple init when debugfs is disabled. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <fa4b832c5a6ec35023a1b997cf658c436619c752 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <8fb8e912afb4c47dec12ea9a5853e7a8db95816f || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <adf1b179c2ff8073c24bf87e5a605fcc5a09798b || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <a9b7b535ba192c6b77e6c15a4c82d853163eab8c | fa4b832c5a6ec35023a1b997cf658c436619c752, 8fb8e912afb4c47dec12ea9a5853e7a8db95816f, adf1b179c2ff8073c24bf87e5a605fcc5a09798b, a9b7b535ba192c6b77e6c15a4c82d853163eab8c |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Oct 29, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: Fix multiple init when debugfs is disabled If bt_debugfs is not created successfully, which happens if either CONFIG_DEBUG_FS or CONFIG_DEBUG_FS_ALLOW_ALL is unset, then iso_init() returns early and does not set iso_inited to true. This means that a subsequent call to iso_init() will result in duplicate calls to proto_register(), bt_sock_register(), etc. With CONFIG_LIST_HARDENED and CONFIG_BUG_ON_DATA_CORRUPTION enabled, the duplicate call to proto_register() triggers this BUG(): list_add double add: new=ffffffffc0b280d0, prev=ffffffffbab56250, next=ffffffffc0b280d0. ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:35! Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI CPU: 2 PID: 887 Comm: bluetoothd Not tainted 6.10.11-1-ao-desktop #1 RIP: 0010:__list_add_valid_or_report+0x9a/0xa0 ... __list_add_valid_or_report+0x9a/0xa0 proto_register+0x2b5/0x340 iso_init+0x23/0x150 [bluetooth] set_iso_socket_func+0x68/0x1b0 [bluetooth] kmem_cache_free+0x308/0x330 hci_sock_sendmsg+0x990/0x9e0 [bluetooth] __sock_sendmsg+0x7b/0x80 sock_write_iter+0x9a/0x110 do_iter_readv_writev+0x11d/0x220 vfs_writev+0x180/0x3e0 do_writev+0xca/0x100 ... This change removes the early return. The check for iso_debugfs being NULL was unnecessary, it is always NULL when iso_inited is false.
Quoted source text, attributed separately from HOL analysis.