{"vulnerability": "CVE-2025-2166", "sightings": [{"uuid": "89b8e0a7-1429-4c56-b970-b1f2613ee482", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21669", "type": "seen", "source": "MISP/24306fae-b16b-4478-9297-d2973cdb583c", "content": "", "creation_timestamp": "2025-08-22T14:52:23.000000Z"}, {"uuid": "97088a9a-43fe-4449-b7fe-38d8220e813e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21668", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/3651", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21668\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\npmdomain: imx8mp-blk-ctrl: add missing loop break condition\n\nCurrently imx8mp_blk_ctrl_remove() will continue the for loop\nuntil an out-of-bounds exception occurs.\n\npstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : dev_pm_domain_detach+0x8/0x48\nlr : imx8mp_blk_ctrl_shutdown+0x58/0x90\nsp : ffffffc084f8bbf0\nx29: ffffffc084f8bbf0 x28: ffffff80daf32ac0 x27: 0000000000000000\nx26: ffffffc081658d78 x25: 0000000000000001 x24: ffffffc08201b028\nx23: ffffff80d0db9490 x22: ffffffc082340a78 x21: 00000000000005b0\nx20: ffffff80d19bc180 x19: 000000000000000a x18: ffffffffffffffff\nx17: ffffffc080a39e08 x16: ffffffc080a39c98 x15: 4f435f464f006c72\nx14: 0000000000000004 x13: ffffff80d0172110 x12: 0000000000000000\nx11: ffffff80d0537740 x10: ffffff80d05376c0 x9 : ffffffc0808ed2d8\nx8 : ffffffc084f8bab0 x7 : 0000000000000000 x6 : 0000000000000000\nx5 : ffffff80d19b9420 x4 : fffffffe03466e60 x3 : 0000000080800077\nx2 : 0000000000000000 x1 : 0000000000000001 x0 : 0000000000000000\nCall trace:\n dev_pm_domain_detach+0x8/0x48\n platform_shutdown+0x2c/0x48\n device_shutdown+0x158/0x268\n kernel_restart_prepare+0x40/0x58\n kernel_kexec+0x58/0xe8\n __do_sys_reboot+0x198/0x258\n __arm64_sys_reboot+0x2c/0x40\n invoke_syscall+0x5c/0x138\n el0_svc_common.constprop.0+0x48/0xf0\n do_el0_svc+0x24/0x38\n el0_svc+0x38/0xc8\n el0t_64_sync_handler+0x120/0x130\n el0t_64_sync+0x190/0x198\nCode: 8128c2d0 ffffffc0 aa1e03e9 d503201f\n\ud83d\udccf Published: 2025-01-31T12:33:02Z\n\ud83d\udccf Modified: 2025-01-31T12:33:02Z\n\ud83d\udd17 References:\n1. https://nvd.nist.gov/vuln/detail/CVE-2025-21668\n2. https://git.kernel.org/stable/c/488a68c948bc52dc2a4554a56fdd99aa67c49b06\n3. https://git.kernel.org/stable/c/699cc10cc3068f9097a506eae7fe178c860dca4e\n4. https://git.kernel.org/stable/c/726efa92e02b460811e8bc6990dd742f03b645ea\n5. https://git.kernel.org/stable/c/926ad31b76b8e229b412536e77cdf828a5cae9c6", "creation_timestamp": "2025-01-31T13:15:02.000000Z"}, {"uuid": "df33ca6f-ae2d-40e0-91a3-0673fe541b83", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2166", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/7525", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-2166\n\ud83d\udd25 CVSS Score: 6.1 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N)\n\ud83d\udd39 Description: The CM FAQ  \u2013 Simplify support with an intuitive FAQ management tool plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of remove_query_arg without appropriate escaping on the URL in all versions up to, and including, 1.2.5. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.\n\ud83d\udccf Published: 2025-03-14T04:22:33.305Z\n\ud83d\udccf Modified: 2025-03-14T04:22:33.305Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/8b8d21cb-fe87-4947-a44b-7d670cf2123e?source=cve\n2. https://plugins.trac.wordpress.org/browser/cm-faq/tags/1.2.4/package/cminds-free.php#L2662\n3. https://plugins.trac.wordpress.org/browser/cm-faq/tags/1.2.5/package/cminds-free.php#L2662\n4. https://plugins.trac.wordpress.org/browser/cm-faq/tags/1.2.6/package/cminds-free.php#L2662", "creation_timestamp": "2025-03-14T04:53:30.000000Z"}, {"uuid": "0b82365f-859b-4682-b531-1f8d0d0ce13f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21667", "type": "seen", "source": "Telegram/_OyaEljbAKCVL_8Cw2-0kGH1x86xOj1kBoP65gKYhYjAYgva", "content": "", "creation_timestamp": "2025-02-06T02:40:19.000000Z"}, {"uuid": "056c8d1b-1b5d-4219-a154-3ae8250c0791", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21666", "type": "seen", "source": "Telegram/whn-Uj5u4qCL1Qo9ZGcHKNtbBFhv43K82k2wWSwPBnfY_Ev3", "content": "", "creation_timestamp": "2025-02-06T02:40:19.000000Z"}, {"uuid": "073e7bf3-4a1f-408a-a95c-061d25266c86", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21665", "type": "seen", "source": "Telegram/NNDfkXhxe9EISMjzUePXjrlUlEHag_XQRkKKljyPXNlN6RlR", "content": "", "creation_timestamp": "2025-02-06T02:40:19.000000Z"}, {"uuid": "8a9bccdd-c5f0-4731-bcea-33e240e85327", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2166", "type": "seen", "source": "https://t.me/cvedetector/20271", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-2166 - WordPress CM FAQ Plugin Reflected Cross-Site Scripting\", \n  \"Content\": \"CVE ID : CVE-2025-2166 \nPublished : March 14, 2025, 5:15 a.m. | 1\u00a0hour, 27\u00a0minutes ago \nDescription : The CM FAQ  \u2013 Simplify support with an intuitive FAQ management tool plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of remove_query_arg without appropriate escaping on the URL in all versions up to, and including, 1.2.5. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. \nSeverity: 6.1 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"14 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-14T08:20:51.000000Z"}, {"uuid": "e2a1ba60-2dbf-4062-9f15-84ca382c7295", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21662", "type": "seen", "source": "https://t.me/cvedetector/15945", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21662 - Mellanox Technologies mlx5 Core Deadlock Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21662 \nPublished : Jan. 21, 2025, 1:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet/mlx5: Fix variable not being completed when function returns  \n  \nWhen cmd_alloc_index(), fails cmd_work_handler() needs  \nto complete ent->slotted before returning early.  \nOtherwise the task which issued the command may hang:  \n  \n   mlx5_core 0000:01:00.0: cmd_work_handler:877:(pid 3880418): failed to allocate command entry  \n   INFO: task kworker/13:2:4055883 blocked for more than 120 seconds.  \n         Not tainted 4.19.90-25.44.v2101.ky10.aarch64 #1  \n   \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message.  \n   kworker/13:2    D    0 4055883      2 0x00000228  \n   Workqueue: events mlx5e_tx_dim_work [mlx5_core]  \n   Call trace:  \n      __switch_to+0xe8/0x150  \n      __schedule+0x2a8/0x9b8  \n      schedule+0x2c/0x88  \n      schedule_timeout+0x204/0x478  \n      wait_for_common+0x154/0x250  \n      wait_for_completion+0x28/0x38  \n      cmd_exec+0x7a0/0xa00 [mlx5_core]  \n      mlx5_cmd_exec+0x54/0x80 [mlx5_core]  \n      mlx5_core_modify_cq+0x6c/0x80 [mlx5_core]  \n      mlx5_core_modify_cq_moderation+0xa0/0xb8 [mlx5_core]  \n      mlx5e_tx_dim_work+0x54/0x68 [mlx5_core]  \n      process_one_work+0x1b0/0x448  \n      worker_thread+0x54/0x468  \n      kthread+0x134/0x138  \n      ret_from_fork+0x10/0x18 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T15:17:28.000000Z"}, {"uuid": "1b557d90-e86d-4c19-b681-fc3796455cbc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21661", "type": "seen", "source": "https://t.me/cvedetector/15944", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21661 - \"Linux GPIO Virtuser Missing Lookup Table Cleanups\"\", \n  \"Content\": \"CVE ID : CVE-2025-21661 \nPublished : Jan. 21, 2025, 1:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ngpio: virtuser: fix missing lookup table cleanups  \n  \nWhen a virtuser device is created via configfs and the probe fails due  \nto an incorrect lookup table, the table is not removed. This prevents  \nsubsequent probe attempts from succeeding, even if the issue is  \ncorrected, unless the device is released. Additionally, cleanup is also  \nneeded in the less likely case of platform_device_register_full()  \nfailure.  \n  \nBesides, a consistent memory leak in lookup_table->dev_id was spotted  \nusing kmemleak by toggling the live state between 0 and 1 with a correct  \nlookup table.  \n  \nIntroduce gpio_virtuser_remove_lookup_table() as the counterpart to the  \nexisting gpio_virtuser_make_lookup_table() and call it from all  \nnecessary points to ensure proper cleanup. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T15:17:27.000000Z"}, {"uuid": "d7b095df-1583-4108-a5fd-aec7a42140e8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21660", "type": "seen", "source": "https://t.me/cvedetector/15943", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21660 - Samba Linux Kernel Buffer Use After Free\", \n  \"Content\": \"CVE ID : CVE-2025-21660 \nPublished : Jan. 21, 2025, 1:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nksmbd: fix unexpectedly changed path in ksmbd_vfs_kern_path_locked  \n  \nWhen `ksmbd_vfs_kern_path_locked` met an error and it is not the last  \nentry, it will exit without restoring changed path buffer. But later this  \nbuffer may be used as the filename for creation. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T15:17:23.000000Z"}, {"uuid": "2c39c340-690e-4134-9209-438f493bca7c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21669", "type": "published-proof-of-concept", "source": "https://t.me/ton618cyber/2585", "content": "#exploit\n1. CVE-2025-20029:\nCommand Injection in TMSH CLI in F5 BIG-IP\nhttps://github.com/mbadanoiu/CVE-2025-20029\n\n2. Dropping a 0 day:\nParallels Desktop Repack Root Privilege Escalation (CVE-2024-34331)\nhttps://jhftss.github.io/Parallels-0-day\n\n3. CVE-2025-21669/CVE-2025-21670:\nvsock/virtio: discard packets if the transport changes / vsock/bpf: return early if transport is not assigned (Linux Kernel)\nhttps://u1f383.github.io/linux/2025/02/24/linux-kernel-some-vsock-vulnerabilities-analysis.html", "creation_timestamp": "2025-02-28T07:48:31.000000Z"}, {"uuid": "b0b75247-dbc4-46a8-96dd-63b7f56b35b6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21660", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgawr6msbs2p", "content": "", "creation_timestamp": "2025-01-21T13:16:12.391062Z"}, {"uuid": "d97974d9-db8d-45a4-a199-5b4acdc571e8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21664", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgawrhli6k2j", "content": "", "creation_timestamp": "2025-01-21T13:16:21.648691Z"}, {"uuid": "aac4ac50-80c8-4a00-8e4a-88da6334c249", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21664", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866578202415415", "content": "", "creation_timestamp": "2025-01-21T13:28:18.643447Z"}, {"uuid": "26712864-74c2-4b71-8f8d-c46f3055efd3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21660", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866519156146659", "content": "", "creation_timestamp": "2025-01-21T13:13:17.836418Z"}, {"uuid": "61426ef0-1f62-4a62-a3ea-fbe066b2d7e9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21662", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866519187536376", "content": "", "creation_timestamp": "2025-01-21T13:13:18.292926Z"}, {"uuid": "7071ec76-2aae-4a63-9e3b-05eacec2e2ed", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21661", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgawrant722e", "content": "", "creation_timestamp": "2025-01-21T13:16:14.417973Z"}, {"uuid": "2a9d1147-6528-43ae-9f1a-bca80e051b3a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21662", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgawrczfzh2s", "content": "", "creation_timestamp": "2025-01-21T13:16:16.972084Z"}, {"uuid": "71675107-937a-4a3f-8c9e-be7d203a46a2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21661", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866519171938126", "content": "", "creation_timestamp": "2025-01-21T13:13:17.958682Z"}, {"uuid": "d1f3a69c-b562-424a-b4a0-049c9f11e1a7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21663", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113866519201601644", "content": "", "creation_timestamp": "2025-01-21T13:13:18.745761Z"}, {"uuid": "8a140c40-f069-4f9b-beac-ab364566421d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21663", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgawrfb2d62h", "content": "", "creation_timestamp": "2025-01-21T13:16:19.484315Z"}, {"uuid": "2a6521b9-899d-4315-b1bb-5dec9397e1b3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21663", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgay2t32vs2g", "content": "", "creation_timestamp": "2025-01-21T13:39:31.209185Z"}, {"uuid": "54462c2a-24c3-4b36-accf-f9faafeabe2e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21664", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgay2trljo25", "content": "", "creation_timestamp": "2025-01-21T13:39:34.387004Z"}, {"uuid": "dcef4e86-97f5-4b24-9b43-e323033740d2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21665", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgzy2w4un72w", "content": "", "creation_timestamp": "2025-01-31T12:16:06.426402Z"}, {"uuid": "92f95945-e25e-42e4-ad02-e97e7c8766d6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21666", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgzy2yjnmf2c", "content": "", "creation_timestamp": "2025-01-31T12:16:08.685357Z"}, {"uuid": "17e41328-daf8-410e-92c3-b5c06463a9ef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21667", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgzy32xbdt2i", "content": "", "creation_timestamp": "2025-01-31T12:16:11.373765Z"}, {"uuid": "8c429abc-50d0-454a-a486-edb351a46bad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21668", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgzy35eixp2b", "content": "", "creation_timestamp": "2025-01-31T12:16:14.155194Z"}, {"uuid": "088eb224-c1f0-4724-8c8a-0f683a34897f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21669", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lgzy37razh2b", "content": "", "creation_timestamp": "2025-01-31T12:16:16.519750Z"}, {"uuid": "21df4868-843f-43ae-9037-051c4c84dfa4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21667", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "8b8ee18f-1fe6-422b-a212-66caa23072bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21667", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/5262", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21667\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\niomap: avoid avoid truncating 64-bit offset to 32 bits\n\non 32-bit kernels, iomap_write_delalloc_scan() was inadvertently using a\n32-bit position due to folio_next_index() returning an unsigned long.\nThis could lead to an infinite loop when writing to an xfs filesystem.\n\ud83d\udccf Published: 2025-01-31T11:25:31.792Z\n\ud83d\udccf Modified: 2025-02-25T08:46:16.716Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/7ca4bd6b754913910151acce00be093f03642725\n2. https://git.kernel.org/stable/c/91371922704c8d82049ef7c2ad974d0a2cd1174d\n3. https://git.kernel.org/stable/c/402ce16421477e27f30b57d6d1a6dc248fa3a4e4\n4. https://git.kernel.org/stable/c/c13094b894de289514d84b8db56d1f2931a0bade", "creation_timestamp": "2025-02-25T09:28:23.000000Z"}, {"uuid": "3e590ac6-567f-41cb-a7b3-154536334c78", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21663", "type": "seen", "source": "https://t.me/cvedetector/15935", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21663 - Nvidia Stmmac Tegra MGBE IOMMU Stream ID Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21663 \nPublished : Jan. 21, 2025, 1:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: stmmac: dwmac-tegra: Read iommu stream id from device tree  \n  \nNvidia's Tegra MGBE controllers require the IOMMU \"Stream ID\" (SID) to be  \nwritten to the MGBE_WRAP_AXI_ASID0_CTRL register.  \n  \nThe current driver is hard coded to use MGBE0's SID for all controllers.  \nThis causes softirq time outs and kernel panics when using controllers  \nother than MGBE0.  \n  \nExample dmesg errors when an ethernet cable is connected to MGBE1:  \n  \n[  116.133290] tegra-mgbe 6910000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx  \n[  121.851283] tegra-mgbe 6910000.ethernet eth1: NETDEV WATCHDOG: CPU: 5: transmit queue 0 timed out 5690 ms  \n[  121.851782] tegra-mgbe 6910000.ethernet eth1: Reset adapter.  \n[  121.892464] tegra-mgbe 6910000.ethernet eth1: Register MEM_TYPE_PAGE_POOL RxQ-0  \n[  121.905920] tegra-mgbe 6910000.ethernet eth1: PHY [stmmac-1:00] driver [Aquantia AQR113] (irq=171)  \n[  121.907356] tegra-mgbe 6910000.ethernet eth1: Enabling Safety Features  \n[  121.907578] tegra-mgbe 6910000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported  \n[  121.908399] tegra-mgbe 6910000.ethernet eth1: registered PTP clock  \n[  121.908582] tegra-mgbe 6910000.ethernet eth1: configuring for phy/10gbase-r link mode  \n[  125.961292] tegra-mgbe 6910000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx  \n[  181.921198] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:  \n[  181.921404] rcu:  7-....: (1 GPs behind) idle=540c/1/0x4000000000000002 softirq=1748/1749 fqs=2337  \n[  181.921684] rcu:  (detected by 4, t=6002 jiffies, g=1357, q=1254 ncpus=8)  \n[  181.921878] Sending NMI from CPU 4 to CPUs 7:  \n[  181.921886] NMI backtrace for cpu 7  \n[  181.922131] CPU: 7 UID: 0 PID: 0 Comm: swapper/7 Kdump: loaded Not tainted 6.13.0-rc3+ #6  \n[  181.922390] Hardware name: NVIDIA CTI Forge + Orin AGX/Jetson, BIOS 202402.1-Unknown 10/28/2024  \n[  181.922658] pstate: 40400009 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)  \n[  181.922847] pc : handle_softirqs+0x98/0x368  \n[  181.922978] lr : __do_softirq+0x18/0x20  \n[  181.923095] sp : ffff80008003bf50  \n[  181.923189] x29: ffff80008003bf50 x28: 0000000000000008 x27: 0000000000000000  \n[  181.923379] x26: ffffce78ea277000 x25: 0000000000000000 x24: 0000001c61befda0  \n[  181.924486] x23: 0000000060400009 x22: ffffce78e99918bc x21: ffff80008018bd70  \n[  181.925568] x20: ffffce78e8bb00d8 x19: ffff80008018bc20 x18: 0000000000000000  \n[  181.926655] x17: ffff318ebe7d3000 x16: ffff800080038000 x15: 0000000000000000  \n[  181.931455] x14: ffff000080816680 x13: ffff318ebe7d3000 x12: 000000003464d91d  \n[  181.938628] x11: 0000000000000040 x10: ffff000080165a70 x9 : ffffce78e8bb0160  \n[  181.945804] x8 : ffff8000827b3160 x7 : f9157b241586f343 x6 : eeb6502a01c81c74  \n[  181.953068] x5 : a4acfcdd2e8096bb x4 : ffffce78ea277340 x3 : 00000000ffffd1e1  \n[  181.960329] x2 : 0000000000000101 x1 : ffffce78ea277340 x0 : ffff318ebe7d3000  \n[  181.967591] Call trace:  \n[  181.970043]  handle_softirqs+0x98/0x368 (P)  \n[  181.974240]  __do_softirq+0x18/0x20  \n[  181.977743]  ____do_softirq+0x14/0x28  \n[  181.981415]  call_on_irq_stack+0x24/0x30  \n[  181.985180]  do_softirq_own_stack+0x20/0x30  \n[  181.989379]  __irq_exit_rcu+0x114/0x140  \n[  181.993142]  irq_exit_rcu+0x14/0x28  \n[  181.996816]  el1_interrupt+0x44/0xb8  \n[  182.000316]  el1h_64_irq_handler+0x14/0x20  \n[  182.004343]  el1h_64_irq+0x80/0x88  \n[  182.007755]  cpuidle_enter_state+0xc4/0x4a8 (P)  \n[  182.012305]  cpuidle_enter+0x3c/0x58  \n[  182.015980]  cpuidle_idle_call+0x128/0x1c0  \n[  182.020005]  do_idle+0xe0/0xf0  \n[  182.023155]  cpu_startup_entry+0x3c/0x48  \n[  182.026917]  secondary_start_kernel+0xdc/0x120  \n[  182.031379]  __secondary_switched+0x74/0x78  \n[  212.971162] rcu: INFO: rcu_pree[...]", "creation_timestamp": "2025-01-21T15:17:14.000000Z"}, {"uuid": "294ec66e-79e8-4426-9e14-aa493cb6f201", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21664", "type": "seen", "source": "https://t.me/cvedetector/15934", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21664 - \"Linux dm thin RCU List DoS\"\", \n  \"Content\": \"CVE ID : CVE-2025-21664 \nPublished : Jan. 21, 2025, 1:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndm thin: make get_first_thin use rcu-safe list first function  \n  \nThe documentation in rculist.h explains the absence of list_empty_rcu()  \nand cautions programmers against relying on a list_empty() ->  \nlist_first() sequence in RCU safe code.  This is because each of these  \nfunctions performs its own READ_ONCE() of the list head.  This can lead  \nto a situation where the list_empty() sees a valid list entry, but the  \nsubsequent list_first() sees a different view of list head state after a  \nmodification.  \n  \nIn the case of dm-thin, this author had a production box crash from a GP  \nfault in the process_deferred_bios path.  This function saw a valid list  \nhead in get_first_thin() but when it subsequently dereferenced that and  \nturned it into a thin_c, it got the inside of the struct pool, since the  \nlist was now empty and referring to itself.  The kernel on which this  \noccurred printed both a warning about a refcount_t being saturated, and  \na UBSAN error for an out-of-bounds cpuid access in the queued spinlock,  \nprior to the fault itself.  When the resulting kdump was examined, it  \nwas possible to see another thread patiently waiting in thin_dtr's  \nsynchronize_rcu.  \n  \nThe thin_dtr call managed to pull the thin_c out of the active thins  \nlist (and have it be the last entry in the active_thins list) at just  \nthe wrong moment which lead to this crash.  \n  \nFortunately, the fix here is straight forward.  Switch get_first_thin()  \nfunction to use list_first_or_null_rcu() which performs just a single  \nREAD_ONCE() and returns NULL if the list is already empty.  \n  \nThis was run against the devicemapper test suite's thin-provisioning  \nsuites for delete and suspend and no regressions were observed. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T15:17:13.000000Z"}, {"uuid": "fb6718c6-2441-4b8d-8808-9b1b3296b1b6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21661", "type": "seen", "source": "Telegram/vE_vt8zf2QZRObk0Hf4Ed28SVKm5HY_SDipUXDEYzgbC1I9S", "content": "", "creation_timestamp": "2025-03-02T11:45:39.000000Z"}, {"uuid": "e5422aef-6a62-4bae-b0e4-46249b8945ab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21669", "type": "published-proof-of-concept", "source": "https://t.me/CyberSecurityTechnologies/11859", "content": "#exploit\n1. CVE-2025-20029:\nCommand Injection in TMSH CLI in F5 BIG-IP\nhttps://github.com/mbadanoiu/CVE-2025-20029\n\n2. Dropping a 0 day:\nParallels Desktop Repack Root Privilege Escalation (CVE-2024-34331)\nhttps://jhftss.github.io/Parallels-0-day\n\n3. CVE-2025-21669/CVE-2025-21670:\nvsock/virtio: discard packets if the transport changes / vsock/bpf: return early if transport is not assigned (Linux Kernel)\nhttps://u1f383.github.io/linux/2025/02/24/linux-kernel-some-vsock-vulnerabilities-analysis.html", "creation_timestamp": "2025-02-26T00:08:02.000000Z"}, {"uuid": "feb75807-2a6c-46f4-9605-4eb7f9bf3f80", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21667", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/3654", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21667\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\niomap: avoid avoid truncating 64-bit offset to 32 bits\n\non 32-bit kernels, iomap_write_delalloc_scan() was inadvertently using a\n32-bit position due to folio_next_index() returning an unsigned long.\nThis could lead to an infinite loop when writing to an xfs filesystem.\n\ud83d\udccf Published: 2025-01-31T12:33:02Z\n\ud83d\udccf Modified: 2025-01-31T12:33:02Z\n\ud83d\udd17 References:\n1. https://nvd.nist.gov/vuln/detail/CVE-2025-21667\n2. https://git.kernel.org/stable/c/402ce16421477e27f30b57d6d1a6dc248fa3a4e4\n3. https://git.kernel.org/stable/c/7ca4bd6b754913910151acce00be093f03642725\n4. https://git.kernel.org/stable/c/91371922704c8d82049ef7c2ad974d0a2cd1174d\n5. https://git.kernel.org/stable/c/c13094b894de289514d84b8db56d1f2931a0bade", "creation_timestamp": "2025-01-31T13:15:08.000000Z"}, {"uuid": "65401956-612a-49eb-85d7-0e3e9e1331b5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21666", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/3653", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21666\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nvsock: prevent null-ptr-deref in vsock_*[has_data|has_space]\n\nRecent reports have shown how we sometimes call vsock_*_has_data()\nwhen a vsock socket has been de-assigned from a transport (see attached\nlinks), but we shouldn't.\n\nPrevious commits should have solved the real problems, but we may have\nmore in the future, so to avoid null-ptr-deref, we can return 0\n(no space, no data available) but with a warning.\n\nThis way the code should continue to run in a nearly consistent state\nand have a warning that allows us to debug future problems.\n\ud83d\udccf Published: 2025-01-31T12:33:02Z\n\ud83d\udccf Modified: 2025-01-31T12:33:02Z\n\ud83d\udd17 References:\n1. https://nvd.nist.gov/vuln/detail/CVE-2025-21666\n2. https://git.kernel.org/stable/c/91751e248256efc111e52e15115840c35d85abaf\n3. https://git.kernel.org/stable/c/9e5fed46ccd2c34c5fa5a9c8825ce4823fdc853e\n4. https://git.kernel.org/stable/c/b52e50dd4fabd12944172bd486a4f4853b7f74dd\n5. https://git.kernel.org/stable/c/bc9c49341f9728c31fe248c5fbba32d2e81a092b\n6. https://git.kernel.org/stable/c/c23d1d4f8efefb72258e9cedce29de10d057f8ca", "creation_timestamp": "2025-01-31T13:15:04.000000Z"}, {"uuid": "cbf024f8-b304-44fc-90b2-7c3d121b7693", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21669", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/3659", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21669\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: discard packets if the transport changes\n\nIf the socket has been de-assigned or assigned to another transport,\nwe must discard any packets received because they are not expected\nand would cause issues when we access vsk->transport.\n\nA possible scenario is described by Hyunwoo Kim in the attached link,\nwhere after a first connect() interrupted by a signal, and a second\nconnect() failed, we can find `vsk->transport` at NULL, leading to a\nNULL pointer dereference.\n\ud83d\udccf Published: 2025-01-31T12:33:02Z\n\ud83d\udccf Modified: 2025-01-31T12:33:02Z\n\ud83d\udd17 References:\n1. https://nvd.nist.gov/vuln/detail/CVE-2025-21669\n2. https://git.kernel.org/stable/c/2cb7c756f605ec02ffe562fb26828e4bcc5fdfc1\n3. https://git.kernel.org/stable/c/6486915fa661584d70e8e7e4068c6c075c67dd6d\n4. https://git.kernel.org/stable/c/677579b641af109613564460a4e3bdcb16850b61\n5. https://git.kernel.org/stable/c/88244163bc7e7b0ce9dd7bf4c8a563b41525c3ee\n6. https://git.kernel.org/stable/c/d88b249e14bd0ee1e46bbe4f456e22e01b8c68de", "creation_timestamp": "2025-01-31T13:15:15.000000Z"}, {"uuid": "60e95cb3-e51f-400a-b4c8-d14196b02d16", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21665", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/3658", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21665\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nfilemap: avoid truncating 64-bit offset to 32 bits\n\nOn 32-bit kernels, folio_seek_hole_data() was inadvertently truncating a\n64-bit value to 32 bits, leading to a possible infinite loop when writing\nto an xfs filesystem.\n\ud83d\udccf Published: 2025-01-31T12:33:02Z\n\ud83d\udccf Modified: 2025-01-31T12:33:02Z\n\ud83d\udd17 References:\n1. https://nvd.nist.gov/vuln/detail/CVE-2025-21665\n2. https://git.kernel.org/stable/c/09528bb1a4123e2a234eac2bc45a0e51e78dab43\n3. https://git.kernel.org/stable/c/280f1fb89afc01e7376f59ae611d54ca69e9f967\n4. https://git.kernel.org/stable/c/64e5fd96330df2ad278d1c4edcca581f26e5f76e\n5. https://git.kernel.org/stable/c/80fc836f3ebe2f2d2d2c80c698b7667974285a04\n6. https://git.kernel.org/stable/c/f505e6c91e7a22d10316665a86d79f84d9f0ba76", "creation_timestamp": "2025-01-31T13:15:11.000000Z"}, {"uuid": "3c3b94e0-4339-43d2-b31c-d6c108355518", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21669", "type": "seen", "source": "https://t.me/cvedetector/16948", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21669 - \"Linux Kernel Virtio Vsock NULL Pointer Dereference\"\", \n  \"Content\": \"CVE ID : CVE-2025-21669 \nPublished : Jan. 31, 2025, 12:15 p.m. | 1\u00a0hour, 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nvsock/virtio: discard packets if the transport changes  \n  \nIf the socket has been de-assigned or assigned to another transport,  \nwe must discard any packets received because they are not expected  \nand would cause issues when we access vsk->transport.  \n  \nA possible scenario is described by Hyunwoo Kim in the attached link,  \nwhere after a first connect() interrupted by a signal, and a second  \nconnect() failed, we can find `vsk->transport` at NULL, leading to a  \nNULL pointer dereference. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"31 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-31T15:22:48.000000Z"}, {"uuid": "96221d50-1b30-4a28-8026-1b8e5b8c0fae", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21669", "type": "published-proof-of-concept", "source": "https://t.me/ton618cyber/6980", "content": "#exploit\n1. CVE-2025-20029:\nCommand Injection in TMSH CLI in F5 BIG-IP\nhttps://github.com/mbadanoiu/CVE-2025-20029\n\n2. Dropping a 0 day:\nParallels Desktop Repack Root Privilege Escalation (CVE-2024-34331)\nhttps://jhftss.github.io/Parallels-0-day\n\n3. CVE-2025-21669/CVE-2025-21670:\nvsock/virtio: discard packets if the transport changes / vsock/bpf: return early if transport is not assigned (Linux Kernel)\nhttps://u1f383.github.io/linux/2025/02/24/linux-kernel-some-vsock-vulnerabilities-analysis.html", "creation_timestamp": "2025-02-28T07:48:31.000000Z"}, {"uuid": "c9e0b5f4-0f6a-4dbe-9a39-6f80091331c5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21661", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgay2ufouh2b", "content": "", "creation_timestamp": "2025-01-21T13:39:36.645195Z"}, {"uuid": "44f257df-378a-4615-beef-2ec24825f97e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21660", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgay2ujc2w2k", "content": "", "creation_timestamp": "2025-01-21T13:39:37.138545Z"}, {"uuid": "cf4fcce0-f241-4a87-9ace-a863dd4b1268", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21662", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lgay2umyzx2i", "content": "", "creation_timestamp": "2025-01-21T13:39:37.642751Z"}, {"uuid": "53b9da2d-a178-48df-835a-762cab79cb32", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21660", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113866687243877568", "content": "", "creation_timestamp": "2025-01-21T13:56:03.404692Z"}, {"uuid": "a46b69d9-6320-4fbc-92e0-9fb5266e886e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21669", "type": "seen", "source": "https://bsky.app/profile/buherator.bsky.social/post/3liwa2ghhtq2x", "content": "", "creation_timestamp": "2025-02-24T11:18:44.076267Z"}, {"uuid": "795b7d91-e89c-4627-b0b4-2ea4ff4bfd86", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21666", "type": "seen", "source": "https://bsky.app/profile/buherator.bsky.social/post/3liwa2ghhtq2x", "content": "", "creation_timestamp": "2025-02-24T11:18:44.228458Z"}]}