{"vulnerability": "CVE-2024-50078", "sightings": [{"uuid": "c1676027-39a0-4d4f-8ce9-f4ddfb73f42e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50078", "type": "seen", "source": "https://t.me/cvedetector/9241", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50078 - Linux Bluetooth List Corruption Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50078 \nPublished : Oct. 29, 2024, 1:15 a.m. | 38\u00a0minutes ago \nDescription : 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  ... \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-29T03:03:55.000000Z"}]}