{"vulnerability": "cve-2025-2202", "sightings": [{"uuid": "1ff3c10d-37af-46a2-8f46-4c0719960cb7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2202", "type": "seen", "source": "MISP/682bdba3-46b7-4a8f-b7be-c6bf4b4f9868", "content": "", "creation_timestamp": "2025-08-13T13:26:35.000000Z"}, {"uuid": "5c7955ce-8587-40d7-a09b-720bdd8dca38", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22027", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "aa5f76c9-d8d9-47ed-98fc-88e44086c994", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22022", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260408", "content": "", "creation_timestamp": "2026-04-07T18:00:00.000000Z"}, {"uuid": "32741c82-ee3a-412e-b07b-9e1c5675cba3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2202", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/7754", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-2202\n\ud83d\udd25 CVSS Score: 6.9 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: Broken access control vulnerability in the Innovaci\u00f3n y Cualificaci\u00f3n local administration plugin ajax.php. This vulnerability allows an attacker to obtain sensitive information about other users such as id, name, login and email.\n\ud83d\udccf Published: 2025-03-17T10:14:37.246Z\n\ud83d\udccf Modified: 2025-03-17T10:14:37.246Z\n\ud83d\udd17 References:\n1. https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-moodle-innovacion-y-cualificacion-plugins", "creation_timestamp": "2025-03-17T10:54:24.000000Z"}, {"uuid": "659c8077-303d-4368-ac0a-ae571a1d24e6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22022", "type": "seen", "source": "Telegram/XWbUozvBnZFZaJxuYJQhgn4U8YQh0aGW0LQo7pqkrJZCpA4", "content": "", "creation_timestamp": "2026-01-11T18:01:52.000000Z"}, {"uuid": "7f948071-08f6-40e3-8f76-ac8aeb3827a1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22026", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "f4cc52cc-7eb8-48fb-8b9c-1a868da9a1e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22025", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "1b05cfd4-f41b-44fc-b19b-dd8e432753b0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22022", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0397/", "content": "", "creation_timestamp": "2026-04-02T17:00:00.000000Z"}, {"uuid": "4e9039c3-b3d9-4c70-92fa-fc53ef671426", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22023", "type": "seen", "source": "https://t.me/cvedetector/23077", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22023 - XHCI USB Driver Isochronous Transfer Ring Buffer Data Loss and UAF Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22023 \nPublished : April 16, 2025, 11:15 a.m. | 14\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nusb: xhci: Don't skip on Stopped - Length Invalid  \n  \nUp until commit d56b0b2ab142 (\"usb: xhci: ensure skipped isoc TDs are  \nreturned when isoc ring is stopped\") in v6.11, the driver didn't skip  \nmissed isochronous TDs when handling Stoppend and Stopped - Length  \nInvalid events. Instead, it erroneously cleared the skip flag, which  \nwould cause the ring to get stuck, as future events won't match the  \nmissed TD which is never removed from the queue until it's cancelled.  \n  \nThis buggy logic seems to have been in place substantially unchanged  \nsince the 3.x series over 10 years ago, which probably speaks first  \nand foremost about relative rarity of this case in normal usage, but  \nby the spec I see no reason why it shouldn't be possible.  \n  \nAfter d56b0b2ab142, TDs are immediately skipped when handling those  \nStopped events. This poses a potential problem in case of Stopped -  \nLength Invalid, which occurs either on completed TDs (likely already  \ngiven back) or Link and No-Op TRBs. Such event won't be recognized  \nas matching any TD (unless it's the rare Link TRB inside a TD) and  \nwill result in skipping all pending TDs, giving them back possibly  \nbefore they are done, risking isoc data loss and maybe UAF by HW.  \n  \nAs a compromise, don't skip and don't clear the skip flag on this  \nkind of event. Then the next event will skip missed TDs. A downside  \nof not handling Stopped - Length Invalid on a Link inside a TD is  \nthat if the TD is cancelled, its actual length will not be updated  \nto account for TRBs (silently) completed before the TD was stopped.  \n  \nI had no luck producing this sequence of completion events so there  \nis no compelling demonstration of any resulting disaster. It may be  \na very rare, obscure condition. The sole motivation for this patch  \nis that if such unlikely event does occur, I'd rather risk reporting  \na cancelled partially done isoc frame as empty than gamble with UAF.  \n  \nThis will be fixed more properly by looking at Stopped event's TRB  \npointer when making skipping decisions, but such rework is unlikely  \nto be backported to v6.12, which will stay around for a few years. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T13:31:30.000000Z"}, {"uuid": "cc6d7d73-1477-49e3-9f3e-5177b67370e7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22022", "type": "seen", "source": "https://t.me/cvedetector/23075", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22022 - Linux USB XHCI Isochronous Endpoint Link Chain Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22022 \nPublished : April 16, 2025, 11:15 a.m. | 14\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nusb: xhci: Apply the link chain quirk on NEC isoc endpoints  \n  \nTwo clearly different specimens of NEC uPD720200 (one with start/stop  \nbug, one without) were seen to cause IOMMU faults after some Missed  \nService Errors. Faulting address is immediately after a transfer ring  \nsegment and patched dynamic debug messages revealed that the MSE was  \nreceived when waiting for a TD near the end of that segment:  \n  \n[ 1.041954] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ffa08fe0  \n[ 1.042120] xhci_hcd: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffa09000 flags=0x0000]  \n[ 1.042146] xhci_hcd: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffa09040 flags=0x0000]  \n  \nIt gets even funnier if the next page is a ring segment accessible to  \nthe HC. Below, it reports MSE in segment at ff1e8000, plows through a  \nzero-filled page at ff1e9000 and starts reporting events for TRBs in  \npage at ff1ea000 every microframe, instead of jumping to seg ff1e6000.  \n  \n[ 7.041671] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ff1e8fe0  \n[ 7.041999] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ff1e8fe0  \n[ 7.042011] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint  \n[ 7.042028] xhci_hcd: All TDs skipped for slot 1 ep 2. Clear skip flag.  \n[ 7.042134] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint  \n[ 7.042138] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 31  \n[ 7.042144] xhci_hcd: Looking for event-dma 00000000ff1ea040 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820  \n[ 7.042259] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint  \n[ 7.042262] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 31  \n[ 7.042266] xhci_hcd: Looking for event-dma 00000000ff1ea050 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820  \n  \nAt some point completion events change from Isoch Buffer Overrun to  \nShort Packet and the HC finally finds cycle bit mismatch in ff1ec000.  \n  \n[ 7.098130] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13  \n[ 7.098132] xhci_hcd: Looking for event-dma 00000000ff1ecc50 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820  \n[ 7.098254] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13  \n[ 7.098256] xhci_hcd: Looking for event-dma 00000000ff1ecc60 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820  \n[ 7.098379] xhci_hcd: Overrun event on slot 1 ep 2  \n  \nIt's possible that data from the isochronous device were written to  \nrandom buffers of pending TDs on other endpoints (either IN or OUT),  \nother devices or even other HCs in the same IOMMU domain.  \n  \nLastly, an error from a different USB device on another HC. Was it  \ncaused by the above? I don't know, but it may have been. The disk  \nwas working without any other issues and generated PCIe traffic to  \nstarve the NEC of upstream BW and trigger those MSEs. The two HCs  \nshared one x1 slot by means of a commercial \"PCIe splitter\" board.  \n  \n[ 7.162604] usb 10-2: reset SuperSpeed USB device number 3 using xhci_hcd  \n[ 7.178990] sd 9:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s  \n[ 7.179001] sd 9:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 04 02 ae 00 00 02 00 00  \n[ 7.179004] I/O error, dev sdb, sector 67284480 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0  \n  \nFortunately, it appears that this ridiculous bug is avoided by setting  \nthe chain bit of Link TRBs on isochronous rings. Other ancient HCs are  \nknown which also expect the bit to be set and they ignore Link TRBs if  \nit's not.[...]", "creation_timestamp": "2025-04-16T13:31:28.000000Z"}, {"uuid": "f7e7bcf0-fc36-401b-b1b2-cffe8e5e7572", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22021", "type": "seen", "source": "https://t.me/cvedetector/23074", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22021 - Kubernetes Cilium Envoy IPv6 SNAT Socket Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22021 \nPublished : April 16, 2025, 11:15 a.m. | 14\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfilter: socket: Lookup orig tuple for IPv6 SNAT  \n  \nnf_sk_lookup_slow_v4 does the conntrack lookup for IPv4 packets to  \nrestore the original 5-tuple in case of SNAT, to be able to find the  \nright socket (if any). Then socket_match() can correctly check whether  \nthe socket was transparent.  \n  \nHowever, the IPv6 counterpart (nf_sk_lookup_slow_v6) lacks this  \nconntrack lookup, making xt_socket fail to match on the socket when the  \npacket was SNATed. Add the same logic to nf_sk_lookup_slow_v6.  \n  \nIPv6 SNAT is used in Kubernetes clusters for pod-to-world packets, as  \npods' addresses are in the fd00::/8 ULA subnet and need to be replaced  \nwith the node's external address. Cilium leverages Envoy to enforce L7  \npolicies, and Envoy uses transparent sockets. Cilium inserts an iptables  \nprerouting rule that matches on `-m socket --transparent` and redirects  \nthe packets to localhost, but it fails to match SNATed IPv6 packets due  \nto that missing conntrack lookup. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T13:31:24.000000Z"}, {"uuid": "a79239b6-2d4c-49d8-b193-13dabdaf75f4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22020", "type": "seen", "source": "https://t.me/cvedetector/23072", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-22020 - Lenovo Linux Kernel MemStick Slab Use After Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-22020 \nPublished : April 16, 2025, 11:15 a.m. | 14\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmemstick: rtsx_usb_ms: Fix slab-use-after-free in rtsx_usb_ms_drv_remove  \n  \nThis fixes the following crash:  \n  \n==================================================================  \nBUG: KASAN: slab-use-after-free in rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms]  \nRead of size 8 at addr ffff888136335380 by task kworker/6:0/140241  \n  \nCPU: 6 UID: 0 PID: 140241 Comm: kworker/6:0 Kdump: loaded Tainted: G            E      6.14.0-rc6+ #1  \nTainted: [E]=UNSIGNED_MODULE  \nHardware name: LENOVO 30FNA1V7CW/1057, BIOS S0EKT54A 07/01/2024  \nWorkqueue: events rtsx_usb_ms_poll_card [rtsx_usb_ms]  \nCall Trace:  \n   \n dump_stack_lvl+0x51/0x70  \n print_address_description.constprop.0+0x27/0x320  \n ? rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms]  \n print_report+0x3e/0x70  \n kasan_report+0xab/0xe0  \n ? rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms]  \n rtsx_usb_ms_poll_card+0x159/0x200 [rtsx_usb_ms]  \n ? __pfx_rtsx_usb_ms_poll_card+0x10/0x10 [rtsx_usb_ms]  \n ? __pfx___schedule+0x10/0x10  \n ? kick_pool+0x3b/0x270  \n process_one_work+0x357/0x660  \n worker_thread+0x390/0x4c0  \n ? __pfx_worker_thread+0x10/0x10  \n kthread+0x190/0x1d0  \n ? __pfx_kthread+0x10/0x10  \n ret_from_fork+0x2d/0x50  \n ? __pfx_kthread+0x10/0x10  \n ret_from_fork_asm+0x1a/0x30  \n   \n  \nAllocated by task 161446:  \n kasan_save_stack+0x20/0x40  \n kasan_save_track+0x10/0x30  \n __kasan_kmalloc+0x7b/0x90  \n __kmalloc_noprof+0x1a7/0x470  \n memstick_alloc_host+0x1f/0xe0 [memstick]  \n rtsx_usb_ms_drv_probe+0x47/0x320 [rtsx_usb_ms]  \n platform_probe+0x60/0xe0  \n call_driver_probe+0x35/0x120  \n really_probe+0x123/0x410  \n __driver_probe_device+0xc7/0x1e0  \n driver_probe_device+0x49/0xf0  \n __device_attach_driver+0xc6/0x160  \n bus_for_each_drv+0xe4/0x160  \n __device_attach+0x13a/0x2b0  \n bus_probe_device+0xbd/0xd0  \n device_add+0x4a5/0x760  \n platform_device_add+0x189/0x370  \n mfd_add_device+0x587/0x5e0  \n mfd_add_devices+0xb1/0x130  \n rtsx_usb_probe+0x28e/0x2e0 [rtsx_usb]  \n usb_probe_interface+0x15c/0x460  \n call_driver_probe+0x35/0x120  \n really_probe+0x123/0x410  \n __driver_probe_device+0xc7/0x1e0  \n driver_probe_device+0x49/0xf0  \n __device_attach_driver+0xc6/0x160  \n bus_for_each_drv+0xe4/0x160  \n __device_attach+0x13a/0x2b0  \n rebind_marked_interfaces.isra.0+0xcc/0x110  \n usb_reset_device+0x352/0x410  \n usbdev_do_ioctl+0xe5c/0x1860  \n usbdev_ioctl+0xa/0x20  \n __x64_sys_ioctl+0xc5/0xf0  \n do_syscall_64+0x59/0x170  \n entry_SYSCALL_64_after_hwframe+0x76/0x7e  \n  \nFreed by task 161506:  \n kasan_save_stack+0x20/0x40  \n kasan_save_track+0x10/0x30  \n kasan_save_free_info+0x36/0x60  \n __kasan_slab_free+0x34/0x50  \n kfree+0x1fd/0x3b0  \n device_release+0x56/0xf0  \n kobject_cleanup+0x73/0x1c0  \n rtsx_usb_ms_drv_remove+0x13d/0x220 [rtsx_usb_ms]  \n platform_remove+0x2f/0x50  \n device_release_driver_internal+0x24b/0x2e0  \n bus_remove_device+0x124/0x1d0  \n device_del+0x239/0x530  \n platform_device_del.part.0+0x19/0xe0  \n platform_device_unregister+0x1c/0x40  \n mfd_remove_devices_fn+0x167/0x170  \n device_for_each_child_reverse+0xc9/0x130  \n mfd_remove_devices+0x6e/0xa0  \n rtsx_usb_disconnect+0x2e/0xd0 [rtsx_usb]  \n usb_unbind_interface+0xf3/0x3f0  \n device_release_driver_internal+0x24b/0x2e0  \n proc_disconnect_claim+0x13d/0x220  \n usbdev_do_ioctl+0xb5e/0x1860  \n usbdev_ioctl+0xa/0x20  \n __x64_sys_ioctl+0xc5/0xf0  \n do_syscall_64+0x59/0x170  \n entry_SYSCALL_64_after_hwframe+0x76/0x7e  \n  \nLast potentially related work creation:  \n kasan_save_stack+0x20/0x40  \n kasan_record_aux_stack+0x85/0x90  \n insert_work+0x29/0x100  \n __queue_work+0x34a/0x540  \n call_timer_fn+0x2a/0x160  \n expire_timers+0x5f/0x1f0  \n __run_timer_base.part.0+0x1b6/0x1e0  \n run_timer_softirq+0x8b/0xe0  \n handle_softirqs+0xf9/0x360  \n __irq_exit_rcu+0x114/0x130  \n sysvec_api[...]", "creation_timestamp": "2025-04-16T13:31:23.000000Z"}, {"uuid": "bda40465-774c-454b-b384-079dbb048775", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2202", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lklcf44zfp2h", "content": "", "creation_timestamp": "2025-03-17T13:51:38.343963Z"}, {"uuid": "6e87d3fe-155a-47eb-9551-6b6bac92c544", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22026", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0291/", "content": "", "creation_timestamp": "2026-03-13T00:00:00.000000Z"}, {"uuid": "c3eec3a9-0f05-454a-8fbb-4882250007a7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22028", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "c75b5a23-54e0-4dab-b88c-582bf42ecd8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22022", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "f8233fd6-fee1-47fc-b174-77097a6c71c5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22026", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "6ccc2a9c-9cef-4893-9771-f916c0c242ff", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22026", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/debian-linux-kernel-multiple-vulnerabilities_20260316", "content": "", "creation_timestamp": "2026-03-16T03:00:00.000000Z"}, {"uuid": "1358002b-ca27-4366-813b-f159d94075ff", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22028", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "2b4afb41-fed8-4264-839d-cbc7e0f62738", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22022", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "f1636eff-c57e-4a80-bbde-74380087cc25", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22026", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12610", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22026\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: don't ignore the return code of svc_proc_register()\n\nCurrently, nfsd_proc_stat_init() ignores the return value of\nsvc_proc_register(). If the procfile creation fails, then the kernel\nwill WARN when it tries to remove the entry later.\n\nFix nfsd_proc_stat_init() to return the same type of pointer as\nsvc_proc_register(), and fix up nfsd_net_init() to check that and fail\nthe nfsd_net construction if it occurs.\n\nsvc_proc_register() can fail if the dentry can't be allocated, or if an\nidentical dentry already exists. The second case is pretty unlikely in\nthe nfsd_net construction codepath, so if this happens, return -ENOMEM.\n\ud83d\udccf Published: 2025-04-16T14:11:47.243Z\n\ud83d\udccf Modified: 2025-04-20T08:31:56.151Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/6a59b70fe71ec66c0dd19e2c279c71846a3fb2f0\n2. https://git.kernel.org/stable/c/e31957a819e60cf0bc9a49408765e6095fd3d046\n3. https://git.kernel.org/stable/c/9d9456185fd5f1891c74354ee297f19538141ead\n4. https://git.kernel.org/stable/c/930b64ca0c511521f0abdd1d57ce52b2a6e3476b", "creation_timestamp": "2025-04-20T09:03:21.000000Z"}, {"uuid": "6764f8bd-9cf9-4e70-816b-3dbc33d5632f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22021", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12009", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22021\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: socket: Lookup orig tuple for IPv6 SNAT\n\nnf_sk_lookup_slow_v4 does the conntrack lookup for IPv4 packets to\nrestore the original 5-tuple in case of SNAT, to be able to find the\nright socket (if any). Then socket_match() can correctly check whether\nthe socket was transparent.\n\nHowever, the IPv6 counterpart (nf_sk_lookup_slow_v6) lacks this\nconntrack lookup, making xt_socket fail to match on the socket when the\npacket was SNATed. Add the same logic to nf_sk_lookup_slow_v6.\n\nIPv6 SNAT is used in Kubernetes clusters for pod-to-world packets, as\npods' addresses are in the fd00::/8 ULA subnet and need to be replaced\nwith the node's external address. Cilium leverages Envoy to enforce L7\npolicies, and Envoy uses transparent sockets. Cilium inserts an iptables\nprerouting rule that matches on `-m socket --transparent` and redirects\nthe packets to localhost, but it fails to match SNATed IPv6 packets due\nto that missing conntrack lookup.\n\ud83d\udccf Published: 2025-04-16T10:20:37.695Z\n\ud83d\udccf Modified: 2025-04-16T10:20:37.695Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/6488b96a79a26e19100ad872622f04e93b638d7f\n2. https://git.kernel.org/stable/c/58ab63d3ded2ca6141357a2b24eee8453d0f871d\n3. https://git.kernel.org/stable/c/1ca2169cc19dca893c7aae6af122852097435d16\n4. https://git.kernel.org/stable/c/1ec43100f7123010730b7ddfc3d5c2eac19e70e7\n5. https://git.kernel.org/stable/c/5251041573850e5020cd447374e23010be698898\n6. https://git.kernel.org/stable/c/2bb139e483f8cbe488d19d8c1135ac3615e2668c\n7. https://git.kernel.org/stable/c/41904cbb343d115931d6bf79aa2c815cac4ef72b\n8. https://git.kernel.org/stable/c/221c27259324ec1404f028d4f5a0f2ae7f63ee23\n9. https://git.kernel.org/stable/c/932b32ffd7604fb00b5c57e239a3cc4d901ccf6e", "creation_timestamp": "2025-04-16T10:55:55.000000Z"}, {"uuid": "ed2a82ad-a5f7-4a14-9a5a-cd08ea7737d3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22023", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12008", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22023\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nusb: xhci: Don't skip on Stopped - Length Invalid\n\nUp until commit d56b0b2ab142 (\"usb: xhci: ensure skipped isoc TDs are\nreturned when isoc ring is stopped\") in v6.11, the driver didn't skip\nmissed isochronous TDs when handling Stoppend and Stopped - Length\nInvalid events. Instead, it erroneously cleared the skip flag, which\nwould cause the ring to get stuck, as future events won't match the\nmissed TD which is never removed from the queue until it's cancelled.\n\nThis buggy logic seems to have been in place substantially unchanged\nsince the 3.x series over 10 years ago, which probably speaks first\nand foremost about relative rarity of this case in normal usage, but\nby the spec I see no reason why it shouldn't be possible.\n\nAfter d56b0b2ab142, TDs are immediately skipped when handling those\nStopped events. This poses a potential problem in case of Stopped -\nLength Invalid, which occurs either on completed TDs (likely already\ngiven back) or Link and No-Op TRBs. Such event won't be recognized\nas matching any TD (unless it's the rare Link TRB inside a TD) and\nwill result in skipping all pending TDs, giving them back possibly\nbefore they are done, risking isoc data loss and maybe UAF by HW.\n\nAs a compromise, don't skip and don't clear the skip flag on this\nkind of event. Then the next event will skip missed TDs. A downside\nof not handling Stopped - Length Invalid on a Link inside a TD is\nthat if the TD is cancelled, its actual length will not be updated\nto account for TRBs (silently) completed before the TD was stopped.\n\nI had no luck producing this sequence of completion events so there\nis no compelling demonstration of any resulting disaster. It may be\na very rare, obscure condition. The sole motivation for this patch\nis that if such unlikely event does occur, I'd rather risk reporting\na cancelled partially done isoc frame as empty than gamble with UAF.\n\nThis will be fixed more properly by looking at Stopped event's TRB\npointer when making skipping decisions, but such rework is unlikely\nto be backported to v6.12, which will stay around for a few years.\n\ud83d\udccf Published: 2025-04-16T10:23:28.381Z\n\ud83d\udccf Modified: 2025-04-16T10:23:28.381Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/6af20ac254cbd0e1178a3542767c9308e209eee5\n2. https://git.kernel.org/stable/c/49cf6f5293aeb706dd672608478336a003f37df6\n3. https://git.kernel.org/stable/c/de9e78167f760a699806793d7c987239e4f6c8c3\n4. https://git.kernel.org/stable/c/58d0a3fab5f4fdc112c16a4c6d382f62097afd1c", "creation_timestamp": "2025-04-16T10:55:51.000000Z"}, {"uuid": "63aa8a10-8801-485b-9259-6c8582f76a4d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2202", "type": "seen", "source": "https://t.me/cvedetector/20449", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-2202 - Innovaci\u00f3n y Cualificaci\u00f3n Local Administration Plugin Access Control Bypass\", \n  \"Content\": \"CVE ID : CVE-2025-2202 \nPublished : March 17, 2025, 11:15 a.m. | 23\u00a0minutes ago \nDescription : Broken access control vulnerability in the Innovaci\u00f3n y Cualificaci\u00f3n local administration plugin ajax.php. This vulnerability allows an attacker to obtain sensitive information about other users such as id, name, login and email. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-17T13:17:00.000000Z"}, {"uuid": "5efcdb2b-8c17-4c3b-b7ed-e35f53d7bf41", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22020", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lrqf52eqqk2p", "content": "", "creation_timestamp": "2025-06-16T16:20:28.398023Z"}]}