https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Thu, 28 May 2026 05:57:40 +0000 https://vulnerability.circl.lu/sighting/64ca9166-b301-4539-8a7c-2ba7d4cc365a/export {"uuid": "64ca9166-b301-4539-8a7c-2ba7d4cc365a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41062", "type": "seen", "source": "https://t.me/cvedetector/1866", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-41062 - \"Bluetooth Linux kernel L2CAP Sock Access Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2024-41062 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbluetooth/l2cap: sync sock recv cb and release \n \nThe problem occurs between the system call to close the sock and hci_rx_work, \nwhere the former releases the sock and the latter accesses it without lock protection. \n \n CPU0 CPU1 \n ---- ---- \n sock_close hci_rx_work \n l2cap_sock_release hci_acldata_packet \n l2cap_sock_kill l2cap_recv_frame \n sk_free l2cap_conless_channel \n l2cap_sock_recv_cb \n \nIf hci_rx_work processes the data that needs to be received before the sock is \nclosed, then everything is normal; Otherwise, the work thread may access the \nreleased sock when receiving data. \n \nAdd a chan mutex in the rx callback of the sock to achieve synchronization between \nthe sock release and recv cb. \n \nSock is dead, so set chan data to NULL, avoid others use invalid sock pointer. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"29 Jul 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:58:11.000000Z"} {"uuid": "64ca9166-b301-4539-8a7c-2ba7d4cc365a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-41062", "type": "seen", "source": "https://t.me/cvedetector/1866", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-41062 - \"Bluetooth Linux kernel L2CAP Sock Access Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2024-41062 \nPublished : July 29, 2024, 3:15 p.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbluetooth/l2cap: sync sock recv cb and release \n \nThe problem occurs between the system call to close the sock and hci_rx_work, \nwhere the former releases the sock and the latter accesses it without lock protection. \n \n CPU0 CPU1 \n ---- ---- \n sock_close hci_rx_work \n l2cap_sock_release hci_acldata_packet \n l2cap_sock_kill l2cap_recv_frame \n sk_free l2cap_conless_channel \n l2cap_sock_recv_cb \n \nIf hci_rx_work processes the data that needs to be received before the sock is \nclosed, then everything is normal; Otherwise, the work thread may access the \nreleased sock when receiving data. \n \nAdd a chan mutex in the rx callback of the sock to achieve synchronization between \nthe sock release and recv cb. \n \nSock is dead, so set chan data to NULL, avoid others use invalid sock pointer. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"29 Jul 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:58:11.000000Z"} https://vulnerability.circl.lu/sighting/64ca9166-b301-4539-8a7c-2ba7d4cc365a/export Mon, 29 Jul 2024 17:58:11 +0000 https://vulnerability.circl.lu/sighting/21a9497c-1cd6-4f6e-8da6-e69c80ea48bb/export {"uuid": "21a9497c-1cd6-4f6e-8da6-e69c80ea48bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-41062", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "21a9497c-1cd6-4f6e-8da6-e69c80ea48bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-41062", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} https://vulnerability.circl.lu/sighting/21a9497c-1cd6-4f6e-8da6-e69c80ea48bb/export Wed, 03 Dec 2025 14:14:49 +0000 https://vulnerability.circl.lu/sighting/8f845a73-5b11-4fad-8511-24143be31e26/export {"uuid": "8f845a73-5b11-4fad-8511-24143be31e26", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-41062", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} {"uuid": "8f845a73-5b11-4fad-8511-24143be31e26", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-41062", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} https://vulnerability.circl.lu/sighting/8f845a73-5b11-4fad-8511-24143be31e26/export Thu, 19 Mar 2026 00:00:00 +0000