https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Sat, 30 May 2026 22:35:58 +0000 https://vulnerability.circl.lu/sighting/e9b6d14d-62c1-4e75-822e-c75ab2d4f9f8/export {"uuid": "e9b6d14d-62c1-4e75-822e-c75ab2d4f9f8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50044", "type": "seen", "source": "https://t.me/cvedetector/8563", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-50044 - Linux Bluetooth RFCOMM Deadlock Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-50044 \nPublished : Oct. 21, 2024, 8:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nBluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change \n \nrfcomm_sk_state_change attempts to use sock_lock so it must never be \ncalled with it locked but rfcomm_sock_ioctl always attempt to lock it \ncausing the following trace: \n \n====================================================== \nWARNING: possible circular locking dependency detected \n6.8.0-syzkaller-08951-gfe46a7dd189e #0 Not tainted \n------------------------------------------------------ \nsyz-executor386/5093 is trying to acquire lock: \nffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1671 [inline] \nffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x5b/0x310 net/bluetooth/rfcomm/sock.c:73 \n \nbut task is already holding lock: \nffff88807badfd28 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x226/0x6a0 net/bluetooth/rfcomm/core.c:491 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"21 Oct 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-21T22:43:17.000000Z"} {"uuid": "e9b6d14d-62c1-4e75-822e-c75ab2d4f9f8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50044", "type": "seen", "source": "https://t.me/cvedetector/8563", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-50044 - Linux Bluetooth RFCOMM Deadlock Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-50044 \nPublished : Oct. 21, 2024, 8:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nBluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change \n \nrfcomm_sk_state_change attempts to use sock_lock so it must never be \ncalled with it locked but rfcomm_sock_ioctl always attempt to lock it \ncausing the following trace: \n \n====================================================== \nWARNING: possible circular locking dependency detected \n6.8.0-syzkaller-08951-gfe46a7dd189e #0 Not tainted \n------------------------------------------------------ \nsyz-executor386/5093 is trying to acquire lock: \nffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1671 [inline] \nffff88807c396258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x5b/0x310 net/bluetooth/rfcomm/sock.c:73 \n \nbut task is already holding lock: \nffff88807badfd28 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x226/0x6a0 net/bluetooth/rfcomm/core.c:491 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"21 Oct 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-21T22:43:17.000000Z"} https://vulnerability.circl.lu/sighting/e9b6d14d-62c1-4e75-822e-c75ab2d4f9f8/export Mon, 21 Oct 2024 22:43:17 +0000 https://vulnerability.circl.lu/sighting/071a79b5-2768-4b9b-91ed-afd10a63e65d/export {"uuid": "071a79b5-2768-4b9b-91ed-afd10a63e65d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50044", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"} {"uuid": "071a79b5-2768-4b9b-91ed-afd10a63e65d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50044", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"} https://vulnerability.circl.lu/sighting/071a79b5-2768-4b9b-91ed-afd10a63e65d/export Thu, 14 Aug 2025 10:00:00 +0000