{"vulnerability": "CVE-2024-4766", "sightings": [{"uuid": "2b72f871-74b0-483b-8577-e47c7025383a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47662", "type": "seen", "source": "https://t.me/cvedetector/7498", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47662 - AMD Display Security Register Read Information Disclosure\", \n  \"Content\": \"CVE ID : CVE-2024-47662 \nPublished : Oct. 9, 2024, 3:15 p.m. | 39\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/amd/display: Remove register from DCN35 DMCUB diagnostic collection  \n  \n[Why]  \nThese registers should not be read from driver and triggering the  \nsecurity violation when DMCUB work times out and diagnostics are  \ncollected blocks Z8 entry.  \n  \n[How]  \nRemove the register read from DCN35. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T18:09:56.000000Z"}, {"uuid": "1d470563-1358-4ace-a8c5-70764fa03c70", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47664", "type": "seen", "source": "https://t.me/cvedetector/7496", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47664 - \"Hisi-Kunpeng SPI Firmware Validation Divide-by-Zero Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-47664 \nPublished : Oct. 9, 2024, 3:15 p.m. | 39\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nspi: hisi-kunpeng: Add verification for the max_frequency provided by the firmware  \n  \nIf the value of max_speed_hz is 0, it may cause a division by zero  \nerror in hisi_calc_effective_speed().  \nThe value of max_speed_hz is provided by firmware.  \nFirmware is generally considered as a trusted domain. However, as  \ndivision by zero errors can cause system failure, for defense measure,  \nthe value of max_speed is validated here. So 0 is regarded as invalid  \nand an error code is returned. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T18:09:55.000000Z"}, {"uuid": "39359980-5db2-4c75-9388-97b205279231", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47666", "type": "seen", "source": "https://t.me/cvedetector/7494", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47666 - \"Marvell PM80xx Memory Corruption\"\", \n  \"Content\": \"CVE ID : CVE-2024-47666 \nPublished : Oct. 9, 2024, 3:15 p.m. | 39\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nscsi: pm80xx: Set phy->enable_completion only when we wait for it  \n  \npm8001_phy_control() populates the enable_completion pointer with a stack  \naddress, sends a PHY_LINK_RESET / PHY_HARD_RESET, waits 300 ms, and  \nreturns. The problem arises when a phy control response comes late.  After  \n300 ms the pm8001_phy_control() function returns and the passed  \nenable_completion stack address is no longer valid. Late phy control  \nresponse invokes complete() on a dangling enable_completion pointer which  \nleads to a kernel crash. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T18:09:53.000000Z"}, {"uuid": "b5d5988a-9331-4e29-bf35-b3c158d072b8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47667", "type": "seen", "source": "https://t.me/cvedetector/7493", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47667 - Texas Instruments AM65x/DRA80xM PCIe Buffer Overflow Hang Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-47667 \nPublished : Oct. 9, 2024, 3:15 p.m. | 39\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nPCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)  \n  \nErrata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0  \n(SPRZ452D_July 2018_Revised December 2019 [1]) mentions when an  \ninbound PCIe TLP spans more than two internal AXI 128-byte bursts,  \nthe bus may corrupt the packet payload and the corrupt data may  \ncause associated applications or the processor to hang.  \n  \nThe workaround for Errata #i2037 is to limit the maximum read  \nrequest size and maximum payload size to 128 bytes. Add workaround  \nfor Errata #i2037 here.  \n  \nThe errata and workaround is applicable only to AM65x SR 1.0 and  \nlater versions of the silicon will have this fixed.  \n  \n[1] ->  \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T18:09:49.000000Z"}, {"uuid": "366e8a28-d6dc-4ce5-9d07-63acd631cda1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47665", "type": "seen", "source": "https://t.me/cvedetector/7492", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47665 - Linux Kernel i3c Mipi-I3c-Hci DMA Alignment Error\", \n  \"Content\": \"CVE ID : CVE-2024-47665 \nPublished : Oct. 9, 2024, 3:15 p.m. | 39\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ni3c: mipi-i3c-hci: Error out instead on BUG_ON() in IBI DMA setup  \n  \nDefinitely condition dma_get_cache_alignment * defined value > 256  \nduring driver initialization is not reason to BUG_ON(). Turn that to  \ngraceful error out with -EINVAL. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T18:09:49.000000Z"}, {"uuid": "4dc62e33-33b2-43dd-b9b4-cf20aec53f2d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47663", "type": "seen", "source": "https://t.me/cvedetector/7491", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47663 - Linux Kernel AD9834 Division by Zero Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-47663 \nPublished : Oct. 9, 2024, 3:15 p.m. | 39\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nstaging: iio: frequency: ad9834: Validate frequency parameter value  \n  \nIn ad9834_write_frequency() clk_get_rate() can return 0. In such case  \nad9834_calc_freqreg() call will lead to division by zero. Checking  \n'if (fout > (clk_freq / 2))' doesn't protect in case of 'fout' is 0.  \nad9834_write_frequency() is called from ad9834_write(), where fout is  \ntaken from text buffer, which can contain any value.  \n  \nModify parameters checking.  \n  \nFound by Linux Verification Center (linuxtesting.org) with SVACE. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T18:09:48.000000Z"}, {"uuid": "611a7510-5e26-4991-942a-b7cc59deba7c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47661", "type": "seen", "source": "https://t.me/cvedetector/7490", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47661 - AMD Display Integer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-47661 \nPublished : Oct. 9, 2024, 3:15 p.m. | 39\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/amd/display: Avoid overflow from uint32_t to uint8_t  \n  \n[WHAT & HOW]  \ndmub_rb_cmd's ramping_boundary has size of uint8_t and it is assigned  \n0xFFFF. Fix it by changing it to uint8_t with value of 0xFF.  \n  \nThis fixes 2 INTEGER_OVERFLOW issues reported by Coverity. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T18:09:47.000000Z"}, {"uuid": "e315762c-2a17-4198-9261-8b31a70f2c96", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47669", "type": "seen", "source": "https://t.me/cvedetector/7488", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47669 - \"Nilfs2 Linux Kernel Log Writing Function Error Handling Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-47669 \nPublished : Oct. 9, 2024, 3:15 p.m. | 39\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnilfs2: fix state management in error path of log writing function  \n  \nAfter commit a694291a6211 (\"nilfs2: separate wait function from  \nnilfs_segctor_write\") was applied, the log writing function  \nnilfs_segctor_do_construct() was able to issue I/O requests continuously  \neven if user data blocks were split into multiple logs across segments,  \nbut two potential flaws were introduced in its error handling.  \n  \nFirst, if nilfs_segctor_begin_construction() fails while creating the  \nsecond or subsequent logs, the log writing function returns without  \ncalling nilfs_segctor_abort_construction(), so the writeback flag set on  \npages/folios will remain uncleared.  This causes page cache operations to  \nhang waiting for the writeback flag.  For example,  \ntruncate_inode_pages_final(), which is called via nilfs_evict_inode() when  \nan inode is evicted from memory, will hang.  \n  \nSecond, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared.   \nAs a result, if the next log write involves checkpoint creation, that's  \nfine, but if a partial log write is performed that does not, inodes with  \nNILFS_I_COLLECTED set are erroneously removed from the \"sc_dirty_files\"  \nlist, and their data and b-tree blocks may not be written to the device,  \ncorrupting the block mapping.  \n  \nFix these issues by uniformly calling nilfs_segctor_abort_construction()  \non failure of each step in the loop in nilfs_segctor_do_construct(),  \nhaving it clean up logs and segment usages according to progress, and  \ncorrecting the conditions for calling nilfs_redirty_inodes() to ensure  \nthat the NILFS_I_COLLECTED flag is cleared. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T18:09:43.000000Z"}, {"uuid": "bd9ce6f9-d89b-4e70-b5f7-c7e5df5ab525", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47668", "type": "seen", "source": "https://t.me/cvedetector/7487", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47668 - Linux kernel Null Pointer Dereference\", \n  \"Content\": \"CVE ID : CVE-2024-47668 \nPublished : Oct. 9, 2024, 3:15 p.m. | 39\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nlib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()  \n  \nIf we need to increase the tree depth, allocate a new node, and then  \nrace with another thread that increased the tree depth before us, we'll  \nstill have a preallocated node that might be used later.  \n  \nIf we then use that node for a new non-root node, it'll still have a  \npointer to the old root instead of being zeroed - fix this by zeroing it  \nin the cmpxchg failure path. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T18:09:42.000000Z"}, {"uuid": "e4ccf72b-9372-4ee6-9795-3dfcae566f79", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47660", "type": "seen", "source": "https://t.me/cvedetector/7470", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47660 - \"Linux filesystem Denial of Service (DoS) Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-47660 \nPublished : Oct. 9, 2024, 2:15 p.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nfsnotify: clear PARENT_WATCHED flags lazily  \n  \nIn some setups directories can have many (usually negative) dentries.  \nHence __fsnotify_update_child_dentry_flags() function can take a  \nsignificant amount of time. Since the bulk of this function happens  \nunder inode->i_lock this causes a significant contention on the lock  \nwhen we remove the watch from the directory as the  \n__fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask()  \nraces with __fsnotify_update_child_dentry_flags() calls from  \n__fsnotify_parent() happening on children. This can lead upto softlockup  \nreports reported by users.  \n  \nFix the problem by calling fsnotify_update_children_dentry_flags() to  \nset PARENT_WATCHED flags only when parent starts watching children.  \n  \nWhen parent stops watching children, clear false positive PARENT_WATCHED  \nflags lazily in __fsnotify_parent() for each accessed child. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T17:19:15.000000Z"}, {"uuid": "110a0708-b5b3-4519-9093-8160ab6c0cf4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-47661", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "56eefd77-2fb0-47f1-90fb-78297c683503", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-47662", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "29566d5f-1aa6-4b19-9801-86d615ec4664", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-47664", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "2445cc1c-cc30-409a-a940-dfb8f71c98c3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-47666", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "90bc2d53-c5f5-40ff-940a-65514e067c2a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47666", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "d74bf8b6-6128-4693-9204-6761bd18ce07", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47668", "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": "2e35c375-2ec0-4d40-a225-b13c8cff953a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47663", "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": "ecaba171-3ce4-4bae-898b-14f1272c45d3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47667", "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": "0c3fb0d9-2c36-42de-ac0b-aa5c1d3da7e4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47669", "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": "536e6c7e-07f2-4ced-9a59-b2ce364b9063", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47666", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0397/", "content": "", "creation_timestamp": "2026-04-02T17:00:00.000000Z"}, {"uuid": "432a0b11-d09f-41fa-9b54-ce37c4b9de85", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47660", "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": "6c8b31d4-12d5-45c7-91c4-dedfac12b895", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-47662", "type": "seen", "source": "https://gist.github.com/stephdl/b118f1f8ba1c82cec1720ff4b164baaa", "content": "", "creation_timestamp": "2026-02-23T16:07:24.000000Z"}, {"uuid": "09ffb03e-a6e1-49af-971e-034359051498", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47665", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "70d3b0c0-f303-47cf-bcad-54791c645e6a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47660", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "1e4f28a8-7201-4a0e-9a5d-385b0700ead7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47661", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "7fe57c86-c76c-4267-aedc-5b5c2fe0a99c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47666", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260408", "content": "", "creation_timestamp": "2026-04-07T18:00:00.000000Z"}]}