{"vulnerability": "cve-2024-5676", "sightings": [{"uuid": "51debfbb-d7fd-41be-950f-5974625c6704", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56760", "type": "seen", "source": "https://t.me/cvedetector/14383", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56760 - Linux kernel PCI/MSI MSI-RISCV Incorrect Legacy Fallback Handling Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56760 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nPCI/MSI: Handle lack of irqdomain gracefully  \n  \nAlexandre observed a warning emitted from pci_msi_setup_msi_irqs() on a  \nRISCV platform which does not provide PCI/MSI support:  \n  \n WARNING: CPU: 1 PID: 1 at drivers/pci/msi/msi.h:121 pci_msi_setup_msi_irqs+0x2c/0x32  \n __pci_enable_msix_range+0x30c/0x596  \n pci_msi_setup_msi_irqs+0x2c/0x32  \n pci_alloc_irq_vectors_affinity+0xb8/0xe2  \n  \nRISCV uses hierarchical interrupt domains and correctly does not implement  \nthe legacy fallback. The warning triggers from the legacy fallback stub.  \n  \nThat warning is bogus as the PCI/MSI layer knows whether a PCI/MSI parent  \ndomain is associated with the device or not. There is a check for MSI-X,  \nwhich has a legacy assumption. But that legacy fallback assumption is only  \nvalid when legacy support is enabled, but otherwise the check should simply  \nreturn -ENOTSUPP.  \n  \nLoongarch tripped over the same problem and blindly enabled legacy support  \nwithout implementing the legacy fallbacks. There are weak implementations  \nwhich return an error, so the problem was papered over.  \n  \nCorrect pci_msi_domain_supports() to evaluate the legacy mode and add  \nthe missing supported check into the MSI enable path to complete it. \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:40.000000Z"}, {"uuid": "0fa032f0-27dc-4f21-ac5f-ee8c4b0e8c35", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56762", "type": "seen", "source": "https://t.me/cvedetector/14382", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56762 - Linux Kernel: io_uring UAF Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56762 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nio_uring/sqpoll: fix sqpoll error handling races  \n  \nBUG: KASAN: slab-use-after-free in __lock_acquire+0x370b/0x4a10 kernel/locking/lockdep.c:5089  \nCall Trace:  \n  \n...  \n_raw_spin_lock_irqsave+0x3d/0x60 kernel/locking/spinlock.c:162  \nclass_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline]  \ntry_to_wake_up+0xb5/0x23c0 kernel/sched/core.c:4205  \nio_sq_thread_park+0xac/0xe0 io_uring/sqpoll.c:55  \nio_sq_thread_finish+0x6b/0x310 io_uring/sqpoll.c:96  \nio_sq_offload_create+0x162/0x11d0 io_uring/sqpoll.c:497  \nio_uring_create io_uring/io_uring.c:3724 [inline]  \nio_uring_setup+0x1728/0x3230 io_uring/io_uring.c:3806  \n...  \n  \nKun Hu reports that the SQPOLL creating error path has UAF, which  \nhappens if io_uring_alloc_task_context() fails and then io_sq_thread()  \nmanages to run and complete before the rest of error handling code,  \nwhich means io_sq_thread_finish() is looking at already killed task.  \n  \nNote that this is mostly theoretical, requiring fault injection on  \nthe allocation side to trigger 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:39.000000Z"}, {"uuid": "f2f4b0cb-e92b-46d4-8afa-f069d60e8461", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56765", "type": "seen", "source": "https://t.me/cvedetector/14380", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56765 - IBM Power pSeries VAS Window Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56765 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \npowerpc/pseries/vas: Add close() callback in vas_vm_ops struct  \n  \nThe mapping VMA address is saved in VAS window struct when the  \npaste address is mapped. This VMA address is used during migration  \nto unmap the paste address if the window is active. The paste  \naddress mapping will be removed when the window is closed or with  \nthe munmap(). But the VMA address in the VAS window is not updated  \nwith munmap() which is causing invalid access during migration.  \n  \nThe KASAN report shows:  \n[16386.254991] BUG: KASAN: slab-use-after-free in reconfig_close_windows+0x1a0/0x4e8  \n[16386.255043] Read of size 8 at addr c00000014a819670 by task drmgr/696928  \n  \n[16386.255096] CPU: 29 UID: 0 PID: 696928 Comm: drmgr Kdump: loaded Tainted: G    B              6.11.0-rc5-nxgzip #2  \n[16386.255128] Tainted: [B]=BAD_PAGE  \n[16386.255148] Hardware name: IBM,9080-HEX Power11 (architected) 0x820200 0xf000007 of:IBM,FW1110.00 (NH1110_016) hv:phyp pSeries  \n[16386.255181] Call Trace:  \n[16386.255202] [c00000016b297660] [c0000000018ad0ac] dump_stack_lvl+0x84/0xe8 (unreliable)  \n[16386.255246] [c00000016b297690] [c0000000006e8a90] print_report+0x19c/0x764  \n[16386.255285] [c00000016b297760] [c0000000006e9490] kasan_report+0x128/0x1f8  \n[16386.255309] [c00000016b297880] [c0000000006eb5c8] __asan_load8+0xac/0xe0  \n[16386.255326] [c00000016b2978a0] [c00000000013f898] reconfig_close_windows+0x1a0/0x4e8  \n[16386.255343] [c00000016b297990] [c000000000140e58] vas_migration_handler+0x3a4/0x3fc  \n[16386.255368] [c00000016b297a90] [c000000000128848] pseries_migrate_partition+0x4c/0x4c4  \n...  \n  \n[16386.256136] Allocated by task 696554 on cpu 31 at 16377.277618s:  \n[16386.256149]  kasan_save_stack+0x34/0x68  \n[16386.256163]  kasan_save_track+0x34/0x80  \n[16386.256175]  kasan_save_alloc_info+0x58/0x74  \n[16386.256196]  __kasan_slab_alloc+0xb8/0xdc  \n[16386.256209]  kmem_cache_alloc_noprof+0x200/0x3d0  \n[16386.256225]  vm_area_alloc+0x44/0x150  \n[16386.256245]  mmap_region+0x214/0x10c4  \n[16386.256265]  do_mmap+0x5fc/0x750  \n[16386.256277]  vm_mmap_pgoff+0x14c/0x24c  \n[16386.256292]  ksys_mmap_pgoff+0x20c/0x348  \n[16386.256303]  sys_mmap+0xd0/0x160  \n...  \n  \n[16386.256350] Freed by task 0 on cpu 31 at 16386.204848s:  \n[16386.256363]  kasan_save_stack+0x34/0x68  \n[16386.256374]  kasan_save_track+0x34/0x80  \n[16386.256384]  kasan_save_free_info+0x64/0x10c  \n[16386.256396]  __kasan_slab_free+0x120/0x204  \n[16386.256415]  kmem_cache_free+0x128/0x450  \n[16386.256428]  vm_area_free_rcu_cb+0xa8/0xd8  \n[16386.256441]  rcu_do_batch+0x2c8/0xcf0  \n[16386.256458]  rcu_core+0x378/0x3c4  \n[16386.256473]  handle_softirqs+0x20c/0x60c  \n[16386.256495]  do_softirq_own_stack+0x6c/0x88  \n[16386.256509]  do_softirq_own_stack+0x58/0x88  \n[16386.256521]  __irq_exit_rcu+0x1a4/0x20c  \n[16386.256533]  irq_exit+0x20/0x38  \n[16386.256544]  interrupt_async_exit_prepare.constprop.0+0x18/0x2c  \n...  \n  \n[16386.256717] Last potentially related work creation:  \n[16386.256729]  kasan_save_stack+0x34/0x68  \n[16386.256741]  __kasan_record_aux_stack+0xcc/0x12c  \n[16386.256753]  __call_rcu_common.constprop.0+0x94/0xd04  \n[16386.256766]  vm_area_free+0x28/0x3c  \n[16386.256778]  remove_vma+0xf4/0x114  \n[16386.256797]  do_vmi_align_munmap.constprop.0+0x684/0x870  \n[16386.256811]  __vm_munmap+0xe0/0x1f8  \n[16386.256821]  sys_munmap+0x54/0x6c  \n[16386.256830]  system_call_exception+0x1a0/0x4a0  \n[16386.256841]  system_call_vectored_common+0x15c/0x2ec  \n  \n[16386.256868] The buggy address belongs to the object at c00000014a819670  \n                which belongs to the cache vm_area_struct of size 168  \n[16386.256887] The buggy address is located 0 bytes inside of  \n                freed 168-byte region [c00000014a819670, c00000014a819718)  \n  \n[16386.256[...]", "creation_timestamp": "2025-01-06T19:26:37.000000Z"}, {"uuid": "9362f737-51cf-412c-9b57-48f99b271810", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56764", "type": "seen", "source": "https://t.me/cvedetector/14379", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56764 - Ubuntu Linux Use-After-Free\", \n  \"Content\": \"CVE ID : CVE-2024-56764 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nublk: detach gendisk from ublk device if add_disk() fails  \n  \nInside ublk_abort_requests(), gendisk is grabbed for aborting all  \ninflight requests. And ublk_abort_requests() is called when exiting  \nthe uring context or handling timeout.  \n  \nIf add_disk() fails, the gendisk may have been freed when calling  \nublk_abort_requests(), so use-after-free can be caused when getting  \ndisk's reference in ublk_abort_requests().  \n  \nFixes the bug by detaching gendisk from ublk device if add_disk() fails. \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:33.000000Z"}, {"uuid": "888bc7bf-a958-408c-942e-63b8c5741e2a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56763", "type": "seen", "source": "https://t.me/cvedetector/14378", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56763 - Linux Kernel Tracing Stack Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56763 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ntracing: Prevent bad count for tracing_cpumask_write  \n  \nIf a large count is provided, it will trigger a warning in bitmap_parse_user.  \nAlso check zero for it. \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:32.000000Z"}, {"uuid": "0b9ea2fd-c024-4cfb-9ed8-bbbb0f39c5b6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56768", "type": "seen", "source": "https://t.me/cvedetector/14377", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56768 - Linux Kernel BPF privileges escalation vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56768 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: Fix bpf_get_smp_processor_id() on !CONFIG_SMP  \n  \nOn x86-64 calling bpf_get_smp_processor_id() in a kernel with CONFIG_SMP  \ndisabled can trigger the following bug, as pcpu_hot is unavailable:  \n  \n [    8.471774] BUG: unable to handle page fault for address: 00000000936a290c  \n [    8.471849] #PF: supervisor read access in kernel mode  \n [    8.471881] #PF: error_code(0x0000) - not-present page  \n  \nFix by inlining a return 0 in the !CONFIG_SMP case. \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:32.000000Z"}, {"uuid": "a98e04a3-f0d6-48ea-8da7-cc62ea500e66", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56767", "type": "seen", "source": "https://t.me/cvedetector/14376", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56767 - Linux Kernel DMAengine at_xdmac Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56767 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndmaengine: at_xdmac: avoid null_prt_deref in at_xdmac_prep_dma_memset  \n  \nThe at_xdmac_memset_create_desc may return NULL, which will lead to a  \nnull pointer dereference. For example, the len input is error, or the  \natchan->free_descs_list is empty and memory is exhausted. Therefore, add  \ncheck to avoid this. \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:31.000000Z"}, {"uuid": "fbbce2a8-e45e-43cc-b3e9-094a75cf2609", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56764", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113782601997679744", "content": "", "creation_timestamp": "2025-01-06T17:32:03.411526Z"}, {"uuid": "12c2cbab-c110-425e-b44c-098180d3fbdb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56763", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "c38be942-6934-452e-a30c-9ff5d12e5e99", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56761", "type": "seen", "source": "https://t.me/cvedetector/14384", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56761 - Linux Kernel x86 IBT WFE Clearing Applier\", \n  \"Content\": \"CVE ID : CVE-2024-56761 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nx86/fred: Clear WFE in missing-ENDBRANCH #CPs  \n  \nAn indirect branch instruction sets the CPU indirect branch tracker  \n(IBT) into WAIT_FOR_ENDBRANCH (WFE) state and WFE stays asserted  \nacross the instruction boundary.  When the decoder finds an  \ninappropriate instruction while WFE is set ENDBR, the CPU raises a #CP  \nfault.  \n  \nFor the \"kernel IBT no ENDBR\" selftest where #CPs are deliberately  \ntriggered, the WFE state of the interrupted context needs to be  \ncleared to let execution continue.  Otherwise when the CPU resumes  \nfrom the instruction that just caused the previous #CP, another  \nmissing-ENDBRANCH #CP is raised and the CPU enters a dead loop.  \n  \nThis is not a problem with IDT because it doesn't preserve WFE and  \nIRET doesn't set WFE.  But FRED provides space on the entry stack  \n(in an expanded CS area) to save and restore the WFE state, thus the  \nWFE state is no longer clobbered, so software must clear it.  \n  \nClear WFE to avoid dead looping in ibt_clear_fred_wfe() and the  \n!ibt_fatal code path when execution is allowed to continue.  \n  \nClobbering WFE in any other circumstance is a security-relevant bug.  \n  \n[ dhansen: changelog rewording ] \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:40.000000Z"}, {"uuid": "6400bc36-ec1c-44be-84b7-c1ccd3300cd2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56766", "type": "seen", "source": "https://t.me/cvedetector/14375", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56766 - \"SamsungLinux Kernel Double Free Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-56766 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmtd: rawnand: fix double free in atmel_pmecc_create_user()  \n  \nThe \"user\" pointer was converted from being allocated with kzalloc() to  \nbeing allocated by devm_kzalloc().  Calling kfree(user) will lead to a  \ndouble free. \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:30.000000Z"}, {"uuid": "d8d4f130-3b3d-40b6-b610-0f04eec86187", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56769", "type": "seen", "source": "https://t.me/cvedetector/14374", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56769 - DVB-USB KMSAN Uninitialized Value in Dib3000 Frontend\", \n  \"Content\": \"CVE ID : CVE-2024-56769 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmedia: dvb-frontends: dib3000mb: fix uninit-value in dib3000_write_reg  \n  \nSyzbot reports [1] an uninitialized value issue found by KMSAN in  \ndib3000_read_reg().  \n  \nLocal u8 rb[2] is used in i2c_transfer() as a read buffer; in case  \nthat call fails, the buffer may end up with some undefined values.  \n  \nSince no elaborate error handling is expected in dib3000_write_reg(),  \nsimply zero out rb buffer to mitigate the problem.  \n  \n[1] Syzkaller report  \ndvb-usb: bulk message failed: -22 (6/0)  \n=====================================================  \nBUG: KMSAN: uninit-value in dib3000mb_attach+0x2d8/0x3c0 drivers/media/dvb-frontends/dib3000mb.c:758  \n dib3000mb_attach+0x2d8/0x3c0 drivers/media/dvb-frontends/dib3000mb.c:758  \n dibusb_dib3000mb_frontend_attach+0x155/0x2f0 drivers/media/usb/dvb-usb/dibusb-mb.c:31  \n dvb_usb_adapter_frontend_init+0xed/0x9a0 drivers/media/usb/dvb-usb/dvb-usb-dvb.c:290  \n dvb_usb_adapter_init drivers/media/usb/dvb-usb/dvb-usb-init.c:90 [inline]  \n dvb_usb_init drivers/media/usb/dvb-usb/dvb-usb-init.c:186 [inline]  \n dvb_usb_device_init+0x25a8/0x3760 drivers/media/usb/dvb-usb/dvb-usb-init.c:310  \n dibusb_probe+0x46/0x250 drivers/media/usb/dvb-usb/dibusb-mb.c:110  \n...  \nLocal variable rb created at:  \n dib3000_read_reg+0x86/0x4e0 drivers/media/dvb-frontends/dib3000mb.c:54  \n dib3000mb_attach+0x123/0x3c0 drivers/media/dvb-frontends/dib3000mb.c:758  \n... \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:26.000000Z"}, {"uuid": "b6962557-c7ce-44b8-8775-52486620375b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56764", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opbutlv2e", "content": "", "creation_timestamp": "2025-01-06T17:43:31.121765Z"}, {"uuid": "7c8aafca-ae39-4a00-9265-f0d1e2627eac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56762", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opbcqvp2r", "content": "", "creation_timestamp": "2025-01-06T17:43:28.745500Z"}, {"uuid": "2ebaf647-86bb-457d-b083-e58986b518d8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56761", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opbkjfr2q", "content": "", "creation_timestamp": "2025-01-06T17:43:29.492979Z"}, {"uuid": "066fb881-20fe-4bc9-9589-eca454f44d41", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56760", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opboajv25", "content": "", "creation_timestamp": "2025-01-06T17:43:29.987447Z"}, {"uuid": "528a15c1-8ca6-47a4-954d-7c73911b9274", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56766", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opcbqov2g", "content": "", "creation_timestamp": "2025-01-06T17:43:33.414525Z"}, {"uuid": "a516c20b-96bc-46f4-b1bf-ff5198fc51fd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56768", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opc3cra2e", "content": "", "creation_timestamp": "2025-01-06T17:43:32.305238Z"}, {"uuid": "9f712311-854c-4725-8f1e-071367a032bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56763", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opc6i7o2h", "content": "", "creation_timestamp": "2025-01-06T17:43:32.813704Z"}, {"uuid": "c5da0649-5dbb-41e3-9fca-196567cff9aa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56769", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opcf26g2h", "content": "", "creation_timestamp": "2025-01-06T17:43:34.072219Z"}, {"uuid": "9e13a0c4-93b3-4fd5-956a-544679025b69", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56767", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opci6od2k", "content": "", "creation_timestamp": "2025-01-06T17:43:34.619751Z"}, {"uuid": "a4d32ddd-6ac9-4a33-a02c-7335244aa93f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56768", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113782655082931400", "content": "", "creation_timestamp": "2025-01-06T17:45:33.313666Z"}, {"uuid": "90f4c787-7d4e-4aa3-8ee0-f37f83f4c669", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56760", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lf3n6lm2gr25", "content": "", "creation_timestamp": "2025-01-06T17:16:14.769396Z"}, {"uuid": "50984407-9ea8-4a77-a0c7-0ed884b6eb70", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56761", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lf3n6nripn2o", "content": "", "creation_timestamp": "2025-01-06T17:16:16.741333Z"}, {"uuid": "cdceabed-a8d7-435b-9929-89d32bc0fc2a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56762", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lf3n6pvc672c", "content": "", "creation_timestamp": "2025-01-06T17:16:19.165865Z"}, {"uuid": "2868fee6-ad96-4abc-81d8-c47e00f67929", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56763", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lf3n6svr5c22", "content": "", "creation_timestamp": "2025-01-06T17:16:22.435205Z"}, {"uuid": "cebe27c0-def3-48e2-bbd4-65891386ae19", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56764", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lf3n6vawg222", "content": "", "creation_timestamp": "2025-01-06T17:16:24.556464Z"}, {"uuid": "67a90631-0e46-4684-bde0-cbf6090db2be", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56765", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lf3n6xsdv222", "content": "", "creation_timestamp": "2025-01-06T17:16:27.333367Z"}, {"uuid": "1e8696f1-8870-4110-ae9c-c93d4a4dc535", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56766", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lf3n6zzy2b2i", "content": "", "creation_timestamp": "2025-01-06T17:16:29.559629Z"}, {"uuid": "1bb1308a-cacf-4f6c-a821-78aecd463c7d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56767", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lf3n75wdo625", "content": "", "creation_timestamp": "2025-01-06T17:16:33.560951Z"}, {"uuid": "1625dcab-615f-4696-9ca3-3cffab70d258", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56768", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lf3n7a4foy2i", "content": "", "creation_timestamp": "2025-01-06T17:16:36.480313Z"}, {"uuid": "27ead954-faa8-45d4-8d1a-dd8f0a437590", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56769", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lf3n7cdaub2l", "content": "", "creation_timestamp": "2025-01-06T17:16:38.389277Z"}]}