Answer in brief
CVE-2024-50078 records a Unknown severity vulnerability in Bluetooth: Call iso_exit() on module unload. 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.
A CVSS score is not reported in the current record. 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 <4af7ba39a1a02e16ee8cd0d3b6c6657f51b8ad7a || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <05f84d86169b2ebac185c5736a256823d42c425b || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <f905a7d95091e0d2605a3a1a157a9351f09ab2e1 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <d458cd1221e9e56da3b2cc5518ad3225caa91f20 | 4af7ba39a1a02e16ee8cd0d3b6c6657f51b8ad7a, 05f84d86169b2ebac185c5736a256823d42c425b, f905a7d95091e0d2605a3a1a157a9351f09ab2e1, d458cd1221e9e56da3b2cc5518ad3225caa91f20 |
| 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: Call iso_exit() on module unload If iso_init() has been called, iso_exit() must be called on module unload. Without that, the struct proto that iso_init() registered with proto_register() becomes invalid, which could cause unpredictable problems later. In my case, with CONFIG_LIST_HARDENED and CONFIG_BUG_ON_DATA_CORRUPTION enabled, loading the module again usually triggers this BUG(): list_add corruption. next->prev should be prev (ffffffffb5355fd0), but was 0000000000000068. (next=ffffffffc0a010d0). ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:29! Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 4159 Comm: modprobe Not tainted 6.10.11-4+bt2-ao-desktop #1 RIP: 0010:__list_add_valid_or_report+0x61/0xa0 ... __list_add_valid_or_report+0x61/0xa0 proto_register+0x299/0x320 hci_sock_init+0x16/0xc0 [bluetooth] bt_init+0x68/0xd0 [bluetooth] __pfx_bt_init+0x10/0x10 [bluetooth] do_one_initcall+0x80/0x2f0 do_init_module+0x8b/0x230 __do_sys_init_module+0x15f/0x190 do_syscall_64+0x68/0x110 ...
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-50078 records a Unknown severity vulnerability in Bluetooth: Call iso_exit() on module unload. 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.
A CVSS score is not reported in the current record. 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 <4af7ba39a1a02e16ee8cd0d3b6c6657f51b8ad7a || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <05f84d86169b2ebac185c5736a256823d42c425b || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <f905a7d95091e0d2605a3a1a157a9351f09ab2e1 || >=ccf74f2390d60a2f9a75ef496d2564abb478f46a <d458cd1221e9e56da3b2cc5518ad3225caa91f20 | 4af7ba39a1a02e16ee8cd0d3b6c6657f51b8ad7a, 05f84d86169b2ebac185c5736a256823d42c425b, f905a7d95091e0d2605a3a1a157a9351f09ab2e1, d458cd1221e9e56da3b2cc5518ad3225caa91f20 |
| 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: Call iso_exit() on module unload If iso_init() has been called, iso_exit() must be called on module unload. Without that, the struct proto that iso_init() registered with proto_register() becomes invalid, which could cause unpredictable problems later. In my case, with CONFIG_LIST_HARDENED and CONFIG_BUG_ON_DATA_CORRUPTION enabled, loading the module again usually triggers this BUG(): list_add corruption. next->prev should be prev (ffffffffb5355fd0), but was 0000000000000068. (next=ffffffffc0a010d0). ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:29! Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 4159 Comm: modprobe Not tainted 6.10.11-4+bt2-ao-desktop #1 RIP: 0010:__list_add_valid_or_report+0x61/0xa0 ... __list_add_valid_or_report+0x61/0xa0 proto_register+0x299/0x320 hci_sock_init+0x16/0xc0 [bluetooth] bt_init+0x68/0xd0 [bluetooth] __pfx_bt_init+0x10/0x10 [bluetooth] do_one_initcall+0x80/0x2f0 do_init_module+0x8b/0x230 __do_sys_init_module+0x15f/0x190 do_syscall_64+0x68/0x110 ...
Quoted source text, attributed separately from HOL analysis.