{"vulnerability": "CVE-2025-2169", "sightings": [{"uuid": "551ed53b-3a01-42ec-8a51-984384437719", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21690", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhtk645xw42c", "content": "", "creation_timestamp": "2025-02-10T16:16:33.935360Z"}, {"uuid": "b23919cc-ba66-4fda-93a5-5415c903e216", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21691", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhtk66l77n2n", "content": "", "creation_timestamp": "2025-02-10T16:16:36.750629Z"}, {"uuid": "de49e494-f83d-4f8c-adfa-1b57de8b8a0f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21692", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhtk6azcaf2n", "content": "", "creation_timestamp": "2025-02-10T16:16:39.370773Z"}, {"uuid": "cd178010-4595-415e-b3eb-e8a9a1111626", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21693", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhtk6dzlf72v", "content": "", "creation_timestamp": "2025-02-10T16:16:42.508168Z"}, {"uuid": "ac6b4a5d-12e7-4600-8546-400dc74e3dbb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2169", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lk3lxtlo7o2s", "content": "", "creation_timestamp": "2025-03-11T08:00:33.001592Z"}, {"uuid": "094f5b68-3f64-44c7-a218-7230bb0951c5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21692", "type": "seen", "source": "https://bsky.app/profile/beikokucyber.bsky.social/post/3lyvpcwbjtf2w", "content": "", "creation_timestamp": "2025-09-15T21:02:23.403151Z"}, {"uuid": "17ca4fb0-a91b-4b7e-b4e6-6d2d84727928", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2169", "type": "seen", "source": "https://t.me/cvedetector/20031", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-2169 - WordPress Currency Switcher Professional Arbitrary Shortcode Execution\", \n  \"Content\": \"CVE ID : CVE-2025-2169 \nPublished : March 11, 2025, 4:15 a.m. | 1\u00a0hour, 37\u00a0minutes ago \nDescription : The The WPCS \u2013 WordPress Currency Switcher Professional plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 1.2.0.4. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes. \nSeverity: 7.3 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"11 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-11T07:35:34.000000Z"}, {"uuid": "980ad3d7-7d33-4a39-af1f-5ae820169b26", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21693", "type": "seen", "source": "https://t.me/cvedetector/17572", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21693 - Linux Kernel zswap Crypto Accomp API CPU Hotplug UAF\", \n  \"Content\": \"CVE ID : CVE-2025-21693 \nPublished : Feb. 10, 2025, 4:15 p.m. | 1\u00a0hour, 27\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmm: zswap: properly synchronize freeing resources during CPU hotunplug  \n  \nIn zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx of the  \ncurrent CPU at the beginning of the operation is retrieved and used  \nthroughout.  However, since neither preemption nor migration are disabled,  \nit is possible that the operation continues on a different CPU.  \n  \nIf the original CPU is hotunplugged while the acomp_ctx is still in use,  \nwe run into a UAF bug as some of the resources attached to the acomp_ctx  \nare freed during hotunplug in zswap_cpu_comp_dead() (i.e.   \nacomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp).  \n  \nThe problem was introduced in commit 1ec3b5fe6eec (\"mm/zswap: move to use  \ncrypto_acomp API for hardware acceleration\") when the switch to the  \ncrypto_acomp API was made.  Prior to that, the per-CPU crypto_comp was  \nretrieved using get_cpu_ptr() which disables preemption and makes sure the  \nCPU cannot go away from under us.  Preemption cannot be disabled with the  \ncrypto_acomp API as a sleepable context is needed.  \n  \nUse the acomp_ctx.mutex to synchronize CPU hotplug callbacks allocating  \nand freeing resources with compression/decompression paths.  Make sure  \nthat acomp_ctx.req is NULL when the resources are freed.  In the  \ncompression/decompression paths, check if acomp_ctx.req is NULL after  \nacquiring the mutex (meaning the CPU was offlined) and retry on the new  \nCPU.  \n  \nThe initialization of acomp_ctx.mutex is moved from the CPU hotplug  \ncallback to the pool initialization where it belongs (where the mutex is  \nallocated).  In addition to adding clarity, this makes sure that CPU  \nhotplug cannot reinitialize a mutex that is already locked by  \ncompression/decompression.  \n  \nPreviously a fix was attempted by holding cpus_read_lock() [1].  This  \nwould have caused a potential deadlock as it is possible for code already  \nholding the lock to fall into reclaim and enter zswap (causing a  \ndeadlock).  A fix was also attempted using SRCU for synchronization, but  \nJohannes pointed out that synchronize_srcu() cannot be used in CPU hotplug  \nnotifiers [2].  \n  \nAlternative fixes that were considered/attempted and could have worked:  \n- Refcounting the per-CPU acomp_ctx. This involves complexity in  \n  handling the race between the refcount dropping to zero in  \n  zswap_[de]compress() and the refcount being re-initialized when the  \n  CPU is onlined.  \n- Disabling migration before getting the per-CPU acomp_ctx [3], but  \n  that's discouraged and is a much bigger hammer than needed, and could  \n  result in subtle performance issues.  \n  \n[1]  \n[2]  \n[3]  \n  \n[yosryahmed@google.com: remove comment]  \n  Link:  \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"10 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-10T18:45:47.000000Z"}, {"uuid": "ed23342d-9195-47f9-8394-c6bf7ba952c4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21699", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/4452", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21699\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: No description available\n\ud83d\udccf Published: 2025-02-12T14:15:33.020\n\ud83d\udccf Modified: N/A\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/2a40a140e11fec699e128170ccaa98b6b82cb503\n2. https://git.kernel.org/stable/c/2b0bd5051ad1c1e9ef4879f18e15a7712c974f3e\n3. https://git.kernel.org/stable/c/4516febe325342555bb09ca5b396fb816d655821\n4. https://git.kernel.org/stable/c/4dd57d1f0e9844311c635a7fb39abce4f2ac5a61\n5. https://git.kernel.org/stable/c/4e3ded34f3f3c9d7ed2aac7be8cf51153646574a\n6. https://git.kernel.org/stable/c/5bb1fd0855bb0abc7d97e44758d6ffed7882d2d0\n7. https://git.kernel.org/stable/c/7c9d9223802fbed4dee1ae301661bf346964c9d2\n8. https://git.kernel.org/stable/c/8c41abc11aa8438c9ed2d973f97e66674c0355df", "creation_timestamp": "2025-02-14T15:12:32.000000Z"}, {"uuid": "bc83d88b-cb3e-4418-9fd6-5c3cd119a3e3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21692", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/51611", "content": "GitHub\u76d1\u63a7\u6d88\u606f\u63d0\u9192\uff01\uff01\uff01 \n\n\u66f4\u65b0\u4e86\uff1aCVE-2025\n\u63cf\u8ff0\uff1aProof of concept source code and misc files for my CVE-2025-21692 exploit, kernel version 6.6.75\nURL\uff1ahttps://github.com/Waletow/Phantom-Registy-Exploit-Cve2025-20682-Runtime-Fud-Lnk\n\n\u6807\u7b7e\uff1a#CVE-2025", "creation_timestamp": "2025-09-14T21:02:24.000000Z"}, {"uuid": "d46fb49f-b3d2-42a0-8702-946215c95347", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21692", "type": "seen", "source": "https://bsky.app/profile/undercode.bsky.social/post/3lzwpyocnzg2r", "content": "", "creation_timestamp": "2025-09-29T00:12:22.782994Z"}, {"uuid": "d083b77c-c2ea-4bff-a5b7-ec77d1875aef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21691", "type": "seen", "source": "https://bsky.app/profile/snee.la/post/3mckik3giqs25", "content": "", "creation_timestamp": "2026-01-16T16:13:45.837358Z"}, {"uuid": "e16ebd7a-7fc6-4dd5-8fdf-193eed774703", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21693", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "efaadbdb-ab3e-4ced-874a-4baa6b7a9133", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21696", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "81b0ca95-c213-434b-80ed-1eb9a10b8351", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21690", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "0664cebd-dfc2-4048-a8cd-0be7d87bdda1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21690", "type": "seen", "source": "Telegram/rVHsmBnrX8yEqJgPGKqSQyFDwuf27yG1jC_c4GOUirc11QuR", "content": "", "creation_timestamp": "2025-02-21T22:10:25.000000Z"}, {"uuid": "d909321f-7526-4e5f-85c5-b6bc9422253b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21692", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/51610", "content": "GitHub\u76d1\u63a7\u6d88\u606f\u63d0\u9192\uff01\uff01\uff01 \n\n\u66f4\u65b0\u4e86\uff1aCVE-2025\n\u63cf\u8ff0\uff1aProof of concept source code and misc files for my CVE-2025-21692 exploit, kernel version 6.6.75\nURL\uff1ahttps://github.com/Waletow/Phantom-Registy-Exploit-Cve2025-20682-Runtime-Fud-Lnk\n\n\u6807\u7b7e\uff1a#CVE-2025", "creation_timestamp": "2025-09-14T21:01:52.000000Z"}, {"uuid": "798d1315-57fc-44aa-810e-148a012093b6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21692", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/51608", "content": "GitHub\u76d1\u63a7\u6d88\u606f\u63d0\u9192\uff01\uff01\uff01 \n\n\u66f4\u65b0\u4e86\uff1aCVE-2025\n\u63cf\u8ff0\uff1aProof of concept source code and misc files for my CVE-2025-21692 exploit, kernel version 6.6.75\nURL\uff1ahttps://github.com/Waletow/Lnk-Exploit-FileBinder-Certificate-Spoofer-Reg-Doc-Cve-Rce\n\n\u6807\u7b7e\uff1a#CVE-2025", "creation_timestamp": "2025-09-14T20:55:00.000000Z"}, {"uuid": "071c6be2-527e-4bcb-9cc4-9adfda999802", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21692", "type": "seen", "source": "https://t.me/cvedetector/17571", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21692 - Linux Kernel: Qdisc ETS Class Array Index Out-of-Bounds Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21692 \nPublished : Feb. 10, 2025, 4:15 p.m. | 1\u00a0hour, 27\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: sched: fix ets qdisc OOB Indexing  \n  \nHaowei Yan  found that ets_class_from_arg() can  \nindex an Out-Of-Bound class in ets_class_from_arg() when passed clid of  \n0. The overflow may cause local privilege escalation.  \n  \n [   18.852298] ------------[ cut here ]------------  \n [   18.853271] UBSAN: array-index-out-of-bounds in net/sched/sch_ets.c:93:20  \n [   18.853743] index 18446744073709551615 is out of range for type 'ets_class [16]'  \n [   18.854254] CPU: 0 UID: 0 PID: 1275 Comm: poc Not tainted 6.12.6-dirty #17  \n [   18.854821] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014  \n [   18.856532] Call Trace:  \n [   18.857441]    \n [   18.858227]  dump_stack_lvl+0xc2/0xf0  \n [   18.859607]  dump_stack+0x10/0x20  \n [   18.860908]  __ubsan_handle_out_of_bounds+0xa7/0xf0  \n [   18.864022]  ets_class_change+0x3d6/0x3f0  \n [   18.864322]  tc_ctl_tclass+0x251/0x910  \n [   18.864587]  ? lock_acquire+0x5e/0x140  \n [   18.865113]  ? __mutex_lock+0x9c/0xe70  \n [   18.866009]  ? __mutex_lock+0xa34/0xe70  \n [   18.866401]  rtnetlink_rcv_msg+0x170/0x6f0  \n [   18.866806]  ? __lock_acquire+0x578/0xc10  \n [   18.867184]  ? __pfx_rtnetlink_rcv_msg+0x10/0x10  \n [   18.867503]  netlink_rcv_skb+0x59/0x110  \n [   18.867776]  rtnetlink_rcv+0x15/0x30  \n [   18.868159]  netlink_unicast+0x1c3/0x2b0  \n [   18.868440]  netlink_sendmsg+0x239/0x4b0  \n [   18.868721]  ____sys_sendmsg+0x3e2/0x410  \n [   18.869012]  ___sys_sendmsg+0x88/0xe0  \n [   18.869276]  ? rseq_ip_fixup+0x198/0x260  \n [   18.869563]  ? rseq_update_cpu_node_id+0x10a/0x190  \n [   18.869900]  ? trace_hardirqs_off+0x5a/0xd0  \n [   18.870196]  ? syscall_exit_to_user_mode+0xcc/0x220  \n [   18.870547]  ? do_syscall_64+0x93/0x150  \n [   18.870821]  ? __memcg_slab_free_hook+0x69/0x290  \n [   18.871157]  __sys_sendmsg+0x69/0xd0  \n [   18.871416]  __x64_sys_sendmsg+0x1d/0x30  \n [   18.871699]  x64_sys_call+0x9e2/0x2670  \n [   18.871979]  do_syscall_64+0x87/0x150  \n [   18.873280]  ? do_syscall_64+0x93/0x150  \n [   18.874742]  ? lock_release+0x7b/0x160  \n [   18.876157]  ? do_user_addr_fault+0x5ce/0x8f0  \n [   18.877833]  ? irqentry_exit_to_user_mode+0xc2/0x210  \n [   18.879608]  ? irqentry_exit+0x77/0xb0  \n [   18.879808]  ? clear_bhb_loop+0x15/0x70  \n [   18.880023]  ? clear_bhb_loop+0x15/0x70  \n [   18.880223]  ? clear_bhb_loop+0x15/0x70  \n [   18.880426]  entry_SYSCALL_64_after_hwframe+0x76/0x7e  \n [   18.880683] RIP: 0033:0x44a957  \n [   18.880851] Code: ff ff e8 fc 00 00 00 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <483d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 8974 24 10  \n [   18.881766] RSP: 002b:00007ffcdd00fad8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e  \n [   18.882149] RAX: ffffffffffffffda RBX: 00007ffcdd010db8 RCX: 000000000044a957  \n [   18.882507] RDX: 0000000000000000 RSI: 00007ffcdd00fb70 RDI: 0000000000000003  \n [   18.885037] RBP: 00007ffcdd010bc0 R08: 000000000703c770 R09: 000000000703c7c0  \n [   18.887203] R10: 0000000000000080 R11: 0000000000000246 R12: 0000000000000001  \n [   18.888026] R13: 00007ffcdd010da8 R14: 00000000004ca7d0 R15: 0000000000000001  \n [   18.888395]    \n [   18.888610] ---[ end trace ]--- \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"10 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-10T18:45:46.000000Z"}, {"uuid": "5d56e0fc-f836-4fd8-9000-d5d90af40e94", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21691", "type": "seen", "source": "https://t.me/cvedetector/17570", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21691 - Linux Kernel cachestat Permission Checking Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21691 \nPublished : Feb. 10, 2025, 4:15 p.m. | 1\u00a0hour, 27\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncachestat: fix page cache statistics permission checking  \n  \nWhen the 'cachestat()' system call was added in commit cf264e1329fb  \n(\"cachestat: implement cachestat syscall\"), it was meant to be a much  \nmore convenient (and performant) version of mincore() that didn't need  \nmapping things into the user virtual address space in order to work.  \n  \nBut it ended up missing the \"check for writability or ownership\" fix for  \nmincore(), done in commit 134fca9063ad (\"mm/mincore.c: make mincore()  \nmore conservative\").  \n  \nThis just adds equivalent logic to 'cachestat()', modified for the file  \ncontext (rather than vma). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"10 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-10T18:45:43.000000Z"}, {"uuid": "01f7729a-ceee-4a6e-91fc-50d79f3cb19f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21690", "type": "seen", "source": "https://t.me/cvedetector/17569", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21690 - VMware StorVSC Denial of Service Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21690 \nPublished : Feb. 10, 2025, 4:15 p.m. | 1\u00a0hour, 27\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nscsi: storvsc: Ratelimit warning logs to prevent VM denial of service  \n  \nIf there's a persistent error in the hypervisor, the SCSI warning for  \nfailed I/O can flood the kernel log and max out CPU utilization,  \npreventing troubleshooting from the VM side. Ratelimit the warning so  \nit doesn't DoS the VM. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"10 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-10T18:45:42.000000Z"}, {"uuid": "30a5facf-7207-42ff-a85c-c4490f14ee51", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21698", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/4291", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21698\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: No description available\n\ud83d\udccf Published: 2025-02-12T14:15:32.900\n\ud83d\udccf Modified: N/A\n\ud83d\udd17 References:\nNo references available.", "creation_timestamp": "2025-02-13T17:15:34.000000Z"}, {"uuid": "5b2668d9-e0b5-411f-be7a-51cbc5ea9532", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21692", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/51581", "content": "GitHub\u76d1\u63a7\u6d88\u606f\u63d0\u9192\uff01\uff01\uff01 \n\n\u66f4\u65b0\u4e86\uff1aCVE-2025\n\u63cf\u8ff0\uff1aProof of concept source code and misc files for my CVE-2025-21692 exploit, kernel version 6.6.75\nURL\uff1ahttps://github.com/volticks/CVE-2025-21692-poc\n\n\u6807\u7b7e\uff1a#CVE-2025", "creation_timestamp": "2025-09-14T16:11:32.000000Z"}, {"uuid": "7e66e544-3136-49f6-b7fa-c4ca2df57587", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21692", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/51580", "content": "GitHub\u76d1\u63a7\u6d88\u606f\u63d0\u9192\uff01\uff01\uff01 \n\n\u66f4\u65b0\u4e86\uff1aCVE-2025\n\u63cf\u8ff0\uff1aProof of concept source code and misc files for my CVE-2025-21692 exploit, kernel version 6.6.75\nURL\uff1ahttps://github.com/volticks/CVE-2025-21692-poc\n\n\u6807\u7b7e\uff1a#CVE-2025", "creation_timestamp": "2025-09-14T16:09:23.000000Z"}, {"uuid": "9736c69e-2162-45d0-815e-06438ec62052", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21692", "type": "published-proof-of-concept", "source": "Telegram/WJizVeVzTrNn9rQzefZR4NZwKXLe6pIHJJmdQfVN3UctWtw", "content": "", "creation_timestamp": "2025-09-14T21:00:05.000000Z"}, {"uuid": "d8cbe2d1-8bc6-4472-9bdc-f102b21cb86d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21693", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lhtx7nr55o2m", "content": "", "creation_timestamp": "2025-02-10T20:10:06.100398Z"}, {"uuid": "1d42fd98-475e-4676-979e-b45b8878faa9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21690", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lhtx7nylbw2p", "content": "", "creation_timestamp": "2025-02-10T20:10:07.312486Z"}, {"uuid": "92fa9a2d-5668-4a07-bad2-76d28f711f14", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21692", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lhtx7o53bj2d", "content": "", "creation_timestamp": "2025-02-10T20:10:07.938330Z"}, {"uuid": "f2b5a170-4ce1-4029-883e-503fc8c916cf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21691", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lhtx7p32dq2o", "content": "", "creation_timestamp": "2025-02-10T20:10:12.198704Z"}, {"uuid": "a263096d-d361-4d84-9db6-b6577eaa3f85", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21694", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113991178485664499", "content": "", "creation_timestamp": "2025-02-12T13:35:48.137719Z"}, {"uuid": "ea82063f-2551-43a3-b83d-843f3ac448ed", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21695", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113991178501779752", "content": "", "creation_timestamp": "2025-02-12T13:35:48.502696Z"}, {"uuid": "5dd69bde-73d3-4467-81fc-768cf9287654", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21696", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113991237502099504", "content": "", "creation_timestamp": "2025-02-12T13:50:48.574183Z"}, {"uuid": "bb9921c7-f550-4c2d-9be7-52be455d5f63", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21697", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113991237536427431", "content": "", "creation_timestamp": "2025-02-12T13:50:49.143032Z"}, {"uuid": "1d1c8051-ddc2-44f2-8eea-4089e70979ed", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21694", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhyefazqvs2x", "content": "", "creation_timestamp": "2025-02-12T14:16:30.216526Z"}, {"uuid": "c78995f9-277b-4460-9d9e-0fcf0dee440b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21695", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhyefdds2j2p", "content": "", "creation_timestamp": "2025-02-12T14:16:32.627189Z"}, {"uuid": "8a27c9ae-4b6c-4246-b345-417acef98026", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21696", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhyeffn7ns2x", "content": "", "creation_timestamp": "2025-02-12T14:16:35.070801Z"}, {"uuid": "144f0c21-fe38-41c6-b6cc-c5e1bf6b9f06", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21697", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhyeficvqt2a", "content": "", "creation_timestamp": "2025-02-12T14:16:38.033661Z"}, {"uuid": "dfbc22cf-a5e1-4291-98d6-0c8e54e7bd26", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21698", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhyefkir4t2g", "content": "", "creation_timestamp": "2025-02-12T14:16:40.251048Z"}, {"uuid": "5bbf1567-f4c5-4402-8991-80f93d4177b4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21699", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhyefmsz5s2d", "content": "", "creation_timestamp": "2025-02-12T14:16:42.519400Z"}, {"uuid": "fd9034e6-d068-4997-a15c-e59d74f51620", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21699", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113992418372512407", "content": "", "creation_timestamp": "2025-02-12T18:51:07.134959Z"}, {"uuid": "1cab719b-5c2b-475a-8ed9-b3223bc6a8ef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21692", "type": "seen", "source": "https://bsky.app/profile/darkwebinformer.com/post/3lyxx4fd76s2x", "content": "", "creation_timestamp": "2025-09-16T18:27:11.431227Z"}, {"uuid": "b0e88c21-abf6-4daf-8573-ea11ee498058", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21697", "type": "seen", "source": "Telegram/dvv4-jUy3rr9EFzZsqoHABWb0232zKxOn54fslm6Hnz27b7W", "content": "", "creation_timestamp": "2025-02-14T21:08:30.000000Z"}, {"uuid": "243cbbb1-55fd-4f8a-ac46-da9991c96638", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21699", "type": "seen", "source": "Telegram/jSSlG1pUryDCxwGzzy38TMxuEG2ZSlg4wLsbmpY6wkYbWD1m", "content": "", "creation_timestamp": "2025-02-14T21:08:29.000000Z"}, {"uuid": "e776db53-4004-4a0e-b5c5-a8e5e5c95900", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21697", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/4451", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21697\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: No description available\n\ud83d\udccf Published: 2025-02-12T14:15:32.787\n\ud83d\udccf Modified: N/A\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/14e0a874488e79086340ba8e2d238cb9596b68a8\n2. https://git.kernel.org/stable/c/1bd6303d08c85072ce40ac01a767ab67195105bd\n3. https://git.kernel.org/stable/c/2a1c88f7ca5c12dff6fa6787492ac910bb9e4407\n4. https://git.kernel.org/stable/c/63195bae1cbf78f1d392b1bc9ae4b03c82d0ebf3\n5. https://git.kernel.org/stable/c/a34050f70e7955a359874dff1a912a748724a140\n6. https://git.kernel.org/stable/c/b22467b1ae104073dcb11aa78562a331cd7fb0e0\n7. https://git.kernel.org/stable/c/e4b5ccd392b92300a2b341705cc4805681094e49", "creation_timestamp": "2025-02-14T15:12:30.000000Z"}, {"uuid": "ccd43ba5-7547-4ab2-be4a-419aa17c50b6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2169", "type": "published-proof-of-concept", "source": "Telegram/nGCSDP4vCltArA3VXeokA5jE1t269Apyi28mkZBPrFAwc4I", "content": "", "creation_timestamp": "2025-03-11T05:36:15.000000Z"}]}