{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2024-50078","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2024-10-21T19:36:19.941Z","datePublished":"2024-10-29T00:50:20.446Z","dateUpdated":"2026-08-05T11:41:27.898Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T11:41:27.898Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: Call iso_exit() on module unload\n\nIf iso_init() has been called, iso_exit() must be called on module\nunload. Without that, the struct proto that iso_init() registered with\nproto_register() becomes invalid, which could cause unpredictable\nproblems later. In my case, with CONFIG_LIST_HARDENED and\nCONFIG_BUG_ON_DATA_CORRUPTION enabled, loading the module again usually\ntriggers this BUG():\n\n  list_add corruption. next->prev should be prev (ffffffffb5355fd0),\n    but was 0000000000000068. (next=ffffffffc0a010d0).\n  ------------[ cut here ]------------\n  kernel BUG at lib/list_debug.c:29!\n  Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI\n  CPU: 1 PID: 4159 Comm: modprobe Not tainted 6.10.11-4+bt2-ao-desktop #1\n  RIP: 0010:__list_add_valid_or_report+0x61/0xa0\n  ...\n    __list_add_valid_or_report+0x61/0xa0\n    proto_register+0x299/0x320\n    hci_sock_init+0x16/0xc0 [bluetooth]\n    bt_init+0x68/0xd0 [bluetooth]\n    __pfx_bt_init+0x10/0x10 [bluetooth]\n    do_one_initcall+0x80/0x2f0\n    do_init_module+0x8b/0x230\n    __do_sys_init_module+0x15f/0x190\n    do_syscall_64+0x68/0x110\n  ..."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - Nothing in this bug involves over-the-air Bluetooth traffic; the dangling pointers are reached purely locally via `open(\"/proc/net/iso\")`, `read(\"/proc/net/protocols\")`, or a `socket(AF_BLUETOOTH, …)` syscall that autoloads the module. Local access to the system is therefore required.\nAC:L - Once the module has been unloaded the stale `proto_list` entry and stale `/proc/net/iso` seq_operations are deterministic — no race, no memory-layout guessing, and the attacker himself triggers the corrupting `proto_register()` by autoloading the module on demand. Every trigger is a single reliable syscall.\nPR:L - The corrupting dereferences are all performed on behalf of an ordinary unprivileged local user: `/proc/net/iso` and `/proc/net/protocols` are world-readable (mode forced to S_IRUGO by proc_create_reg), and `request_module(\"net-pf-31\")` in `__sock_create()` has no capability gate. No CAP_NET_ADMIN or CAP_SYS_MODULE is needed by the attacker to hit the freed memory.\nUI:N - The vulnerable condition is a persistent system state left behind by an ordinary lifecycle event (driver reload, dongle hotplug handling, rfkill/hardening scripts, `modprobe -r bluetooth` during troubleshooting), not an action a victim must be tricked into performing as part of the attack. After that state exists, the attacker acts entirely alone.\nS:U - The corruption is confined to kernel memory within the same security authority; there is no VM, IOMMU, or sandbox boundary crossed. Standard kernel-local privilege-escalation scope.\nC:H - `proto_seq_printf()` walks the stale `proto_list` entry and prints `proto->name` (`%s`) and `proto->owner->name` from freed module memory straight to userspace, and the stale `bt_seq_ops`/`iso_sk_list` in `/proc/net/iso` yield an attacker-steerable read primitive over reallocated kernel memory.\nI:H - The next `proto_register()` performs `__list_add`, writing a kernel pointer into the freed module region, and `/proc/net/iso` makes an indirect call through a `seq_operations` function pointer read from that same freed memory — a use-after-free giving both write and control-flow-hijack primitives once the module vmalloc range is reused.\nA:H - The reported symptom is a hard kernel panic — `list_add corruption … kernel BUG at lib/list_debug.c:29` / `Oops: invalid opcode` — reproducibly triggered on module reload, which any unprivileged user can force via AF_BLUETOOTH socket autoload. Uninstrumented kernels instead suffer arbitrary memory corruption that crashes just as readily."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["net/bluetooth/af_bluetooth.c"],"versions":[{"version":"ccf74f2390d60a2f9a75ef496d2564abb478f46a","lessThan":"4af7ba39a1a02e16ee8cd0d3b6c6657f51b8ad7a","status":"affected","versionType":"git"},{"version":"ccf74f2390d60a2f9a75ef496d2564abb478f46a","lessThan":"05f84d86169b2ebac185c5736a256823d42c425b","status":"affected","versionType":"git"},{"version":"ccf74f2390d60a2f9a75ef496d2564abb478f46a","lessThan":"f905a7d95091e0d2605a3a1a157a9351f09ab2e1","status":"affected","versionType":"git"},{"version":"ccf74f2390d60a2f9a75ef496d2564abb478f46a","lessThan":"d458cd1221e9e56da3b2cc5518ad3225caa91f20","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["net/bluetooth/af_bluetooth.c"],"versions":[{"version":"6.0","status":"affected"},{"version":"0","lessThan":"6.0","status":"unaffected","versionType":"semver"},{"version":"6.1.114","lessThanOrEqual":"6.1.*","status":"unaffected","versionType":"semver"},{"version":"6.6.58","lessThanOrEqual":"6.6.*","status":"unaffected","versionType":"semver"},{"version":"6.11.5","lessThanOrEqual":"6.11.*","status":"unaffected","versionType":"semver"},{"version":"6.12","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"6.1.114"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"6.6.58"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"6.11.5"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"6.12"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/4af7ba39a1a02e16ee8cd0d3b6c6657f51b8ad7a"},{"url":"https://git.kernel.org/stable/c/05f84d86169b2ebac185c5736a256823d42c425b"},{"url":"https://git.kernel.org/stable/c/f905a7d95091e0d2605a3a1a157a9351f09ab2e1"},{"url":"https://git.kernel.org/stable/c/d458cd1221e9e56da3b2cc5518ad3225caa91f20"}],"title":"Bluetooth: Call iso_exit() on module unload","x_generator":{"engine":"bippy-1.2.0"}},"adp":[{"metrics":[{"cvssV3_1":{"scope":"UNCHANGED","version":"3.1","baseScore":5.5,"attackVector":"LOCAL","baseSeverity":"MEDIUM","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","integrityImpact":"NONE","userInteraction":"NONE","attackComplexity":"LOW","availabilityImpact":"HIGH","privilegesRequired":"LOW","confidentialityImpact":"NONE"}},{"other":{"type":"ssvc","content":{"id":"CVE-2024-50078","role":"CISA Coordinator","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"version":"2.0.3","timestamp":"2025-10-01T20:23:25.456239Z"}}}],"problemTypes":[{"descriptions":[{"lang":"en","type":"CWE","description":"CWE-noinfo Not enough information"}]}],"title":"CISA ADP Vulnrichment","providerMetadata":{"orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP","dateUpdated":"2025-10-01T20:27:20.959Z"}},{"title":"CVE Program Container","references":[{"url":"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"}],"providerMetadata":{"orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE","dateUpdated":"2025-11-03T22:25:12.840Z"}}]}}