https://db.gcve.eu/sightings/feed 2026-05-15T17:11:17.350687+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent sightings. https://db.gcve.eu/sighting/27c454ed-9f96-4df5-a56c-d1e75b6c664e/export 2026-05-15T17:11:17.555511+00:00 cedric http://db.gcve.eu/user/cedric {"uuid": "27c454ed-9f96-4df5-a56c-d1e75b6c664e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21641", "type": "seen", "source": "https://t.me/cvedetector/15833", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-21641 - Linux Kernel MPTCP Sysctl Blackhole Timeout Use-After-Free Vulnerability\", \n \"Content\": \"CVE ID : CVE-2025-21641 \nPublished : Jan. 19, 2025, 11:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nmptcp: sysctl: blackhole timeout: avoid using current->nsproxy \n \nAs mentioned in the previous commit, using the 'net' structure via \n'current' is not recommended for different reasons: \n \n- Inconsistency: getting info from the reader's/writer's netns vs only \n from the opener's netns. \n \n- current->nsproxy can be NULL in some cases, resulting in an 'Oops' \n (null-ptr-deref), e.g. when the current task is exiting, as spotted by \n syzbot [1] using acct(2). \n \nThe 'pernet' structure can be obtained from the table->data using \ncontainer_of(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Jan 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-19T13:07:20.000000Z"} 2025-01-19T13:07:20+00:00 https://db.gcve.eu/sighting/70ebe098-2d45-4760-9750-74b4889854bb/export 2026-05-15T17:11:17.555446+00:00 cedric http://db.gcve.eu/user/cedric {"uuid": "70ebe098-2d45-4760-9750-74b4889854bb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21642", "type": "seen", "source": "https://t.me/cvedetector/15834", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-21642 - Microsoft Windows MPTCP Linux Kernel NetSysctl Use After Free Vulnerability\", \n \"Content\": \"CVE ID : CVE-2025-21642 \nPublished : Jan. 19, 2025, 11:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nmptcp: sysctl: sched: avoid using current->nsproxy \n \nUsing the 'net' structure via 'current' is not recommended for different \nreasons. \n \nFirst, if the goal is to use it to read or write per-netns data, this is \ninconsistent with how the \"generic\" sysctl entries are doing: directly \nby only using pointers set to the table entry, e.g. table->data. Linked \nto that, the per-netns data should always be obtained from the table \nlinked to the netns it had been created for, which may not coincide with \nthe reader's or writer's netns. \n \nAnother reason is that access to current->nsproxy->netns can oops if \nattempted when current->nsproxy had been dropped when the current task \nis exiting. This is what syzbot found, when using acct(2): \n \n Oops: general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] PREEMPT SMP KASAN PTI \n KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] \n CPU: 1 UID: 0 PID: 5924 Comm: syz-executor Not tainted 6.13.0-rc5-syzkaller-00004-gccb98ccef0e5 #0 \n Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 \n RIP: 0010:proc_scheduler+0xc6/0x3c0 net/mptcp/ctrl.c:125 \n Code: 03 42 80 3c 38 00 0f 85 fe 02 00 00 4d 8b a4 24 08 09 00 00 48 b8 00 00 00 00 00 fc ff df 49 8d 7c 24 28 48 89 fa 48 c1 ea 03 <803c 02 00 0f 85 cc 02 00 00 4d 8b 7c 24 28 48 8d 84 24 c8 00 00 \n RSP: 0018:ffffc900034774e8 EFLAGS: 00010206 \n \n RAX: dffffc0000000000 RBX: 1ffff9200068ee9e RCX: ffffc90003477620 \n RDX: 0000000000000005 RSI: ffffffff8b08f91e RDI: 0000000000000028 \n RBP: 0000000000000001 R08: ffffc90003477710 R09: 0000000000000040 \n R10: 0000000000000040 R11: 00000000726f7475 R12: 0000000000000000 \n R13: ffffc90003477620 R14: ffffc90003477710 R15: dffffc0000000000 \n FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 \n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 \n CR2: 00007fee3cd452d8 CR3: 000000007d116000 CR4: 00000000003526f0 \n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 \n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 \n Call Trace: \n \n proc_sys_call_handler+0x403/0x5d0 fs/proc/proc_sysctl.c:601 \n __kernel_write_iter+0x318/0xa80 fs/read_write.c:612 \n __kernel_write+0xf6/0x140 fs/read_write.c:632 \n do_acct_process+0xcb0/0x14a0 kernel/acct.c:539 \n acct_pin_kill+0x2d/0x100 kernel/acct.c:192 \n pin_kill+0x194/0x7c0 fs/fs_pin.c:44 \n mnt_pin_kill+0x61/0x1e0 fs/fs_pin.c:81 \n cleanup_mnt+0x3ac/0x450 fs/namespace.c:1366 \n task_work_run+0x14e/0x250 kernel/task_work.c:239 \n exit_task_work include/linux/task_work.h:43 [inline] \n do_exit+0xad8/0x2d70 kernel/exit.c:938 \n do_group_exit+0xd3/0x2a0 kernel/exit.c:1087 \n get_signal+0x2576/0x2610 kernel/signal.c:3017 \n arch_do_signal_or_restart+0x90/0x7e0 arch/x86/kernel/signal.c:337 \n exit_to_user_mode_loop kernel/entry/common.c:111 [inline] \n exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline] \n __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] \n syscall_exit_to_user_mode+0x150/0x2a0 kernel/entry/common.c:218 \n do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89 \n entry_SYSCALL_64_after_hwframe+0x77/0x7f \n RIP: 0033:0x7fee3cb87a6a \n Code: Unable to access opcode bytes at 0x7fee3cb87a40. \n RSP: 002b:00007fffcccac688 EFLAGS: 00000202 ORIG_RAX: 0000000000000037 \n RAX: 0000000000000000 RBX: 00007fffcccac710 RCX: 00007fee3cb87a6a \n RDX: 0000000000000041 RSI: 0000000000000000 RDI: 0000000000000003 \n RBP: 0000000000000003 R08: 00007fffcccac6ac R09: 00007fffcccacac7 \n R10: 00007fffcccac710 R11: 0000000000000202 R12: 00007f[...]", "creation_timestamp": "2025-01-19T13:07:21.000000Z"} 2025-01-19T13:07:21+00:00 https://db.gcve.eu/sighting/9acc42ce-8076-4864-a376-e100c3352965/export 2026-05-15T17:11:17.555390+00:00 cedric http://db.gcve.eu/user/cedric {"uuid": "9acc42ce-8076-4864-a376-e100c3352965", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21643", "type": "seen", "source": "https://t.me/cvedetector/15836", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-21643 - \"CIFS Netfs Linux Kernel Async DIO Handling Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2025-21643 \nPublished : Jan. 19, 2025, 11:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnetfs: Fix kernel async DIO \n \nNetfslib needs to be able to handle kernel-initiated asynchronous DIO that \nis supplied with a bio_vec[] array. Currently, because of the async flag, \nthis gets passed to netfs_extract_user_iter() which throws a warning and \nfails because it only handles IOVEC and UBUF iterators. This can be \ntriggered through a combination of cifs and a loopback blockdev with \nsomething like: \n \n mount //my/cifs/share /foo \n dd if=/dev/zero of=/foo/m0 bs=4K count=1K \n losetup --sector-size 4096 --direct-io=on /dev/loop2046 /foo/m0 \n echo hello >/dev/loop2046 \n \nThis causes the following to appear in syslog: \n \n WARNING: CPU: 2 PID: 109 at fs/netfs/iterator.c:50 netfs_extract_user_iter+0x170/0x250 [netfs] \n \nand the write to fail. \n \nFix this by removing the check in netfs_unbuffered_write_iter_locked() that \ncauses async kernel DIO writes to be handled as userspace writes. Note \nthat this change relies on the kernel caller maintaining the existence of \nthe bio_vec array (or kvec[] or folio_queue) until the op is complete. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Jan 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-19T13:07:22.000000Z"} 2025-01-19T13:07:22+00:00 https://db.gcve.eu/sighting/259146a1-985c-4c7a-b9d1-849c58e3c2c1/export 2026-05-15T17:11:17.555328+00:00 cedric http://db.gcve.eu/user/cedric {"uuid": "259146a1-985c-4c7a-b9d1-849c58e3c2c1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21644", "type": "seen", "source": "https://t.me/cvedetector/15837", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-21644 - \"Intel Xeon DRM GuC Firmware Wedge Null Pointer Dereference Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2025-21644 \nPublished : Jan. 19, 2025, 11:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/xe: Fix tlb invalidation when wedging \n \nIf GuC fails to load, the driver wedges, but in the process it tries to \ndo stuff that may not be initialized yet. This moves the \nxe_gt_tlb_invalidation_init() to be done earlier: as its own doc says, \nit's a software-only initialization and should had been named with the \n_early() suffix. \n \nMove it to be called by xe_gt_init_early(), so the locks and seqno are \ninitialized, avoiding a NULL ptr deref when wedging: \n \n xe 0000:03:00.0: [drm] *ERROR* GT0: load failed: status: Reset = 0, BootROM = 0x50, UKernel = 0x00, MIA = 0x00, Auth = 0x01 \n xe 0000:03:00.0: [drm] *ERROR* GT0: firmware signature verification failed \n xe 0000:03:00.0: [drm] *ERROR* CRITICAL: Xe has declared device 0000:03:00.0 as wedged. \n ... \n BUG: kernel NULL pointer dereference, address: 0000000000000000 \n #PF: supervisor read access in kernel mode \n #PF: error_code(0x0000) - not-present page \n PGD 0 P4D 0 \n Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI \n CPU: 9 UID: 0 PID: 3908 Comm: modprobe Tainted: G U W 6.13.0-rc4-xe+ #3 \n Tainted: [U]=USER, [W]=WARN \n Hardware name: Intel Corporation Alder Lake Client Platform/AlderLake-S ADP-S DDR5 UDIMM CRB, BIOS ADLSFWI1.R00.3275.A00.2207010640 07/01/2022 \n RIP: 0010:xe_gt_tlb_invalidation_reset+0x75/0x110 [xe] \n \nThis can be easily triggered by poking the GuC binary to force a \nsignature failure. There will still be an extra message, \n \n xe 0000:03:00.0: [drm] *ERROR* GT0: GuC mmio request 0x4100: no reply 0x4100 \n \nbut that's better than a NULL ptr deref. \n \n(cherry picked from commit 5001ef3af8f2c972d6fd9c5221a8457556f8bea6) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"19 Jan 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-19T13:07:26.000000Z"} 2025-01-19T13:07:26+00:00 https://db.gcve.eu/sighting/bd18a346-1153-4997-8945-d8d0c9a4cd9b/export 2026-05-15T17:11:17.555269+00:00 cedric http://db.gcve.eu/user/cedric {"uuid": "bd18a346-1153-4997-8945-d8d0c9a4cd9b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2164", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/7658", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-2164\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 pixelstats plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'post_id' and 'sortby' parameters in all versions up to, and including, 0.8.2 due to insufficient input sanitization and output escaping. 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-15T03:23:23.563Z\n\ud83d\udccf Modified: 2025-03-15T03:23:23.563Z\n\ud83d\udd17 References:\n1. https://www.wordfence.com/threat-intel/vulnerabilities/id/8683bc00-1136-42c4-a256-84b2cac1d575?source=cve\n2. https://plugins.trac.wordpress.org/browser/pixelstats/tags/0.8.2/pixelstats.php#L331\n3. https://plugins.trac.wordpress.org/browser/pixelstats/tags/0.8.2/pixelstats.php#L664\n4. https://wordpress.org/plugins/pixelstats/", "creation_timestamp": "2025-03-15T03:49:05.000000Z"} 2025-03-15T03:49:05+00:00 https://db.gcve.eu/sighting/104a0176-f6c5-44c5-bac6-32dcba898dd6/export 2026-05-15T17:11:17.555194+00:00 cedric http://db.gcve.eu/user/cedric {"uuid": "104a0176-f6c5-44c5-bac6-32dcba898dd6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2164", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lkfdkxmyou2n", "content": "", "creation_timestamp": "2025-03-15T04:56:49.508860Z"} 2025-03-15T04:56:49.508860+00:00 https://db.gcve.eu/sighting/4baf14bd-f426-4660-bb71-3a8b651909f6/export 2026-05-15T17:11:17.555098+00:00 cedric http://db.gcve.eu/user/cedric {"uuid": "4baf14bd-f426-4660-bb71-3a8b651909f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2164", "type": "seen", "source": "https://t.me/cvedetector/20353", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-2164 - WordPress Pixelstats Reflected Cross-Site Scripting\", \n \"Content\": \"CVE ID : CVE-2025-2164 \nPublished : March 15, 2025, 4:15 a.m. | 1\u00a0hour, 35\u00a0minutes ago \nDescription : The pixelstats plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'post_id' and 'sortby' parameters in all versions up to, and including, 0.8.2 due to insufficient input sanitization and output escaping. 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\": \"15 Mar 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-15T06:55:39.000000Z"} 2025-03-15T06:55:39+00:00 https://db.gcve.eu/sighting/2e548fa8-98a1-4aea-8f77-77518ed9f2e7/export 2026-05-15T17:11:17.554889+00:00 cedric http://db.gcve.eu/user/cedric {"uuid": "2e548fa8-98a1-4aea-8f77-77518ed9f2e7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21648", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} 2025-12-03T14:14:49.267740+00:00 https://db.gcve.eu/sighting/9f856087-2124-42db-967f-12dacbe47e2b/export 2026-05-15T17:11:17.554603+00:00 cedric http://db.gcve.eu/user/cedric {"uuid": "9f856087-2124-42db-967f-12dacbe47e2b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21645", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} 2026-03-19T00:00:00+00:00 https://db.gcve.eu/sighting/cbc043cc-22f5-425c-a8a6-ac76d773035e/export 2026-05-15T17:11:17.552371+00:00 cedric http://db.gcve.eu/user/cedric {"uuid": "cbc043cc-22f5-425c-a8a6-ac76d773035e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21649", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} 2026-03-19T00:00:00+00:00