https://db.gcve.eu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Tue, 10 Nov 2026 01:11:33 +0000 https://db.gcve.eu/sighting/7e864b35-2435-4c49-bc12-1b5a970ae256/export {"uuid": "7e864b35-2435-4c49-bc12-1b5a970ae256", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-56757", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} {"uuid": "7e864b35-2435-4c49-bc12-1b5a970ae256", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-56757", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} https://db.gcve.eu/sighting/7e864b35-2435-4c49-bc12-1b5a970ae256/export Thu, 19 Mar 2026 00:00:00 +0000 https://db.gcve.eu/sighting/c41e8e67-52ca-4f47-add7-7eae99e0942d/export {"uuid": "c41e8e67-52ca-4f47-add7-7eae99e0942d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56756", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3me6zzvrufd2z", "content": "", "creation_timestamp": "2026-02-06T13:45:16.445791Z"} {"uuid": "c41e8e67-52ca-4f47-add7-7eae99e0942d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56756", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3me6zzvrufd2z", "content": "", "creation_timestamp": "2026-02-06T13:45:16.445791Z"} https://db.gcve.eu/sighting/c41e8e67-52ca-4f47-add7-7eae99e0942d/export Fri, 06 Feb 2026 13:45:16 +0000 https://db.gcve.eu/sighting/a089100a-2da2-458a-a789-9456729fd989/export {"uuid": "a089100a-2da2-458a-a789-9456729fd989", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56759", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "a089100a-2da2-458a-a789-9456729fd989", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56759", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} https://db.gcve.eu/sighting/a089100a-2da2-458a-a789-9456729fd989/export Wed, 03 Dec 2025 14:14:49 +0000 https://db.gcve.eu/sighting/1aa34a9f-91d5-478d-b978-dfb5f75af6d0/export {"uuid": "1aa34a9f-91d5-478d-b978-dfb5f75af6d0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56751", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "1aa34a9f-91d5-478d-b978-dfb5f75af6d0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56751", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} https://db.gcve.eu/sighting/1aa34a9f-91d5-478d-b978-dfb5f75af6d0/export Wed, 03 Dec 2025 14:14:49 +0000 https://db.gcve.eu/sighting/003b9ed8-f581-42ac-bb18-cf0b0feef654/export {"uuid": "003b9ed8-f581-42ac-bb18-cf0b0feef654", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56754", "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": "003b9ed8-f581-42ac-bb18-cf0b0feef654", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56754", "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://db.gcve.eu/sighting/003b9ed8-f581-42ac-bb18-cf0b0feef654/export Thu, 14 Aug 2025 10:00:00 +0000 https://db.gcve.eu/sighting/7cca49b1-7451-4e52-b8ff-cfbeaecc9c1d/export {"uuid": "7cca49b1-7451-4e52-b8ff-cfbeaecc9c1d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56756", "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": "7cca49b1-7451-4e52-b8ff-cfbeaecc9c1d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56756", "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://db.gcve.eu/sighting/7cca49b1-7451-4e52-b8ff-cfbeaecc9c1d/export Thu, 14 Aug 2025 10:00:00 +0000 https://db.gcve.eu/sighting/6c15e5ed-6be7-4cef-9203-af64d8aae803/export {"uuid": "6c15e5ed-6be7-4cef-9203-af64d8aae803", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56759", "type": "seen", "source": "https://t.me/cvedetector/14387", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56759 - Linux Btrfs Use-After-Free Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-56759 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbtrfs: fix use-after-free when COWing tree bock and tracing is enabled \n \nWhen a COWing a tree block, at btrfs_cow_block(), and we have the \ntracepoint trace_btrfs_cow_block() enabled and preemption is also enabled \n(CONFIG_PREEMPT=y), we can trigger a use-after-free in the COWed extent \nbuffer while inside the tracepoint code. This is because in some paths \nthat call btrfs_cow_block(), such as btrfs_search_slot(), we are holding \nthe last reference on the extent buffer @buf so btrfs_force_cow_block() \ndrops the last reference on the @buf extent buffer when it calls \nfree_extent_buffer_stale(buf), which schedules the release of the extent \nbuffer with RCU. This means that if we are on a kernel with preemption, \nthe current task may be preempted before calling trace_btrfs_cow_block() \nand the extent buffer already released by the time trace_btrfs_cow_block() \nis called, resulting in a use-after-free. \n \nFix this by moving the trace_btrfs_cow_block() from btrfs_cow_block() to \nbtrfs_force_cow_block() before the COWed extent buffer is freed. \nThis also has a side effect of invoking the tracepoint in the tree defrag \ncode, at defrag.c:btrfs_realloc_node(), since btrfs_force_cow_block() is \ncalled there, but this is fine and it was actually missing there. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"06 Jan 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-06T19:26:46.000000Z"} {"uuid": "6c15e5ed-6be7-4cef-9203-af64d8aae803", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56759", "type": "seen", "source": "https://t.me/cvedetector/14387", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56759 - Linux Btrfs Use-After-Free Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-56759 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbtrfs: fix use-after-free when COWing tree bock and tracing is enabled \n \nWhen a COWing a tree block, at btrfs_cow_block(), and we have the \ntracepoint trace_btrfs_cow_block() enabled and preemption is also enabled \n(CONFIG_PREEMPT=y), we can trigger a use-after-free in the COWed extent \nbuffer while inside the tracepoint code. This is because in some paths \nthat call btrfs_cow_block(), such as btrfs_search_slot(), we are holding \nthe last reference on the extent buffer @buf so btrfs_force_cow_block() \ndrops the last reference on the @buf extent buffer when it calls \nfree_extent_buffer_stale(buf), which schedules the release of the extent \nbuffer with RCU. This means that if we are on a kernel with preemption, \nthe current task may be preempted before calling trace_btrfs_cow_block() \nand the extent buffer already released by the time trace_btrfs_cow_block() \nis called, resulting in a use-after-free. \n \nFix this by moving the trace_btrfs_cow_block() from btrfs_cow_block() to \nbtrfs_force_cow_block() before the COWed extent buffer is freed. \nThis also has a side effect of invoking the tracepoint in the tree defrag \ncode, at defrag.c:btrfs_realloc_node(), since btrfs_force_cow_block() is \ncalled there, but this is fine and it was actually missing there. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"06 Jan 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-06T19:26:46.000000Z"} https://db.gcve.eu/sighting/6c15e5ed-6be7-4cef-9203-af64d8aae803/export Mon, 06 Jan 2025 19:26:46 +0000 https://db.gcve.eu/sighting/1e72e3c3-1ca0-4d21-b491-0ee509125220/export {"uuid": "1e72e3c3-1ca0-4d21-b491-0ee509125220", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56758", "type": "seen", "source": "https://t.me/cvedetector/14386", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56758 - Linux Btrfs NULL Pointer Dereference Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-56758 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbtrfs: check folio mapping after unlock in relocate_one_folio() \n \nWhen we call btrfs_read_folio() to bring a folio uptodate, we unlock the \nfolio. The result of that is that a different thread can modify the \nmapping (like remove it with invalidate) before we call folio_lock(). \nThis results in an invalid page and we need to try again. \n \nIn particular, if we are relocating concurrently with aborting a \ntransaction, this can result in a crash like the following: \n \n BUG: kernel NULL pointer dereference, address: 0000000000000000 \n PGD 0 P4D 0 \n Oops: 0000 [#1] SMP \n CPU: 76 PID: 1411631 Comm: kworker/u322:5 \n Workqueue: events_unbound btrfs_reclaim_bgs_work \n RIP: 0010:set_page_extent_mapped+0x20/0xb0 \n RSP: 0018:ffffc900516a7be8 EFLAGS: 00010246 \n RAX: ffffea009e851d08 RBX: ffffea009e0b1880 RCX: 0000000000000000 \n RDX: 0000000000000000 RSI: ffffc900516a7b90 RDI: ffffea009e0b1880 \n RBP: 0000000003573000 R08: 0000000000000001 R09: ffff88c07fd2f3f0 \n R10: 0000000000000000 R11: 0000194754b575be R12: 0000000003572000 \n R13: 0000000003572fff R14: 0000000000100cca R15: 0000000005582fff \n FS: 0000000000000000(0000) GS:ffff88c07fd00000(0000) knlGS:0000000000000000 \n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 \n CR2: 0000000000000000 CR3: 000000407d00f002 CR4: 00000000007706f0 \n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 \n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 \n PKRU: 55555554 \n Call Trace: \n \n ? __die+0x78/0xc0 \n ? page_fault_oops+0x2a8/0x3a0 \n ? __switch_to+0x133/0x530 \n ? wq_worker_running+0xa/0x40 \n ? exc_page_fault+0x63/0x130 \n ? asm_exc_page_fault+0x22/0x30 \n ? set_page_extent_mapped+0x20/0xb0 \n relocate_file_extent_cluster+0x1a7/0x940 \n relocate_data_extent+0xaf/0x120 \n relocate_block_group+0x20f/0x480 \n btrfs_relocate_block_group+0x152/0x320 \n btrfs_relocate_chunk+0x3d/0x120 \n btrfs_reclaim_bgs_work+0x2ae/0x4e0 \n process_scheduled_works+0x184/0x370 \n worker_thread+0xc6/0x3e0 \n ? blk_add_timer+0xb0/0xb0 \n kthread+0xae/0xe0 \n ? flush_tlb_kernel_range+0x90/0x90 \n ret_from_fork+0x2f/0x40 \n ? flush_tlb_kernel_range+0x90/0x90 \n ret_from_fork_asm+0x11/0x20 \n \n \nThis occurs because cleanup_one_transaction() calls \ndestroy_delalloc_inodes() which calls invalidate_inode_pages2() which \ntakes the folio_lock before setting mapping to NULL. We fail to check \nthis, and subsequently call set_extent_mapping(), which assumes that \nmapping != NULL (in fact it asserts that in debug mode) \n \nNote that the \"fixes\" patch here is not the one that introduced the \nrace (the very first iteration of this code from 2009) but a more recent \nchange that made this particular crash happen in practice. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"06 Jan 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-06T19:26:45.000000Z"} {"uuid": "1e72e3c3-1ca0-4d21-b491-0ee509125220", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56758", "type": "seen", "source": "https://t.me/cvedetector/14386", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56758 - Linux Btrfs NULL Pointer Dereference Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-56758 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbtrfs: check folio mapping after unlock in relocate_one_folio() \n \nWhen we call btrfs_read_folio() to bring a folio uptodate, we unlock the \nfolio. The result of that is that a different thread can modify the \nmapping (like remove it with invalidate) before we call folio_lock(). \nThis results in an invalid page and we need to try again. \n \nIn particular, if we are relocating concurrently with aborting a \ntransaction, this can result in a crash like the following: \n \n BUG: kernel NULL pointer dereference, address: 0000000000000000 \n PGD 0 P4D 0 \n Oops: 0000 [#1] SMP \n CPU: 76 PID: 1411631 Comm: kworker/u322:5 \n Workqueue: events_unbound btrfs_reclaim_bgs_work \n RIP: 0010:set_page_extent_mapped+0x20/0xb0 \n RSP: 0018:ffffc900516a7be8 EFLAGS: 00010246 \n RAX: ffffea009e851d08 RBX: ffffea009e0b1880 RCX: 0000000000000000 \n RDX: 0000000000000000 RSI: ffffc900516a7b90 RDI: ffffea009e0b1880 \n RBP: 0000000003573000 R08: 0000000000000001 R09: ffff88c07fd2f3f0 \n R10: 0000000000000000 R11: 0000194754b575be R12: 0000000003572000 \n R13: 0000000003572fff R14: 0000000000100cca R15: 0000000005582fff \n FS: 0000000000000000(0000) GS:ffff88c07fd00000(0000) knlGS:0000000000000000 \n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 \n CR2: 0000000000000000 CR3: 000000407d00f002 CR4: 00000000007706f0 \n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 \n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 \n PKRU: 55555554 \n Call Trace: \n \n ? __die+0x78/0xc0 \n ? page_fault_oops+0x2a8/0x3a0 \n ? __switch_to+0x133/0x530 \n ? wq_worker_running+0xa/0x40 \n ? exc_page_fault+0x63/0x130 \n ? asm_exc_page_fault+0x22/0x30 \n ? set_page_extent_mapped+0x20/0xb0 \n relocate_file_extent_cluster+0x1a7/0x940 \n relocate_data_extent+0xaf/0x120 \n relocate_block_group+0x20f/0x480 \n btrfs_relocate_block_group+0x152/0x320 \n btrfs_relocate_chunk+0x3d/0x120 \n btrfs_reclaim_bgs_work+0x2ae/0x4e0 \n process_scheduled_works+0x184/0x370 \n worker_thread+0xc6/0x3e0 \n ? blk_add_timer+0xb0/0xb0 \n kthread+0xae/0xe0 \n ? flush_tlb_kernel_range+0x90/0x90 \n ret_from_fork+0x2f/0x40 \n ? flush_tlb_kernel_range+0x90/0x90 \n ret_from_fork_asm+0x11/0x20 \n \n \nThis occurs because cleanup_one_transaction() calls \ndestroy_delalloc_inodes() which calls invalidate_inode_pages2() which \ntakes the folio_lock before setting mapping to NULL. We fail to check \nthis, and subsequently call set_extent_mapping(), which assumes that \nmapping != NULL (in fact it asserts that in debug mode) \n \nNote that the \"fixes\" patch here is not the one that introduced the \nrace (the very first iteration of this code from 2009) but a more recent \nchange that made this particular crash happen in practice. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"06 Jan 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-06T19:26:45.000000Z"} https://db.gcve.eu/sighting/1e72e3c3-1ca0-4d21-b491-0ee509125220/export Mon, 06 Jan 2025 19:26:45 +0000 https://db.gcve.eu/sighting/396d93dd-edbb-41f3-a2be-2e3e914df8ad/export {"uuid": "396d93dd-edbb-41f3-a2be-2e3e914df8ad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56757", "type": "seen", "source": "https://t.me/cvedetector/14385", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56757 - \"Mediatek Bluetooth btusb Kernel Panic Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2024-56757 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nBluetooth: btusb: mediatek: add intf release flow when usb disconnect \n \nMediaTek claim an special usb intr interface for ISO data transmission. \nThe interface need to be released before unregistering hci device when \nusb disconnect. Removing BT usb dongle without properly releasing the \ninterface may cause Kernel panic while unregister hci device. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"06 Jan 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-06T19:26:44.000000Z"} {"uuid": "396d93dd-edbb-41f3-a2be-2e3e914df8ad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56757", "type": "seen", "source": "https://t.me/cvedetector/14385", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-56757 - \"Mediatek Bluetooth btusb Kernel Panic Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2024-56757 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nBluetooth: btusb: mediatek: add intf release flow when usb disconnect \n \nMediaTek claim an special usb intr interface for ISO data transmission. \nThe interface need to be released before unregistering hci device when \nusb disconnect. Removing BT usb dongle without properly releasing the \ninterface may cause Kernel panic while unregister hci device. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"06 Jan 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-06T19:26:44.000000Z"} https://db.gcve.eu/sighting/396d93dd-edbb-41f3-a2be-2e3e914df8ad/export Mon, 06 Jan 2025 19:26:44 +0000 https://db.gcve.eu/sighting/1d5693df-6a41-4e38-ba29-b4a3d2e8dfa9/export {"uuid": "1d5693df-6a41-4e38-ba29-b4a3d2e8dfa9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56758", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opbxzd22b", "content": "", "creation_timestamp": "2025-01-06T17:43:31.705011Z"} {"uuid": "1d5693df-6a41-4e38-ba29-b4a3d2e8dfa9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56758", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opbxzd22b", "content": "", "creation_timestamp": "2025-01-06T17:43:31.705011Z"} https://db.gcve.eu/sighting/1d5693df-6a41-4e38-ba29-b4a3d2e8dfa9/export Mon, 06 Jan 2025 17:43:31 +0000