https://vulnerability.circl.lu/sightings/feed 2026-09-03T09:08:52.079160+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/39a1bd71-3da9-4670-ab5e-85592dda02a0/export 2026-09-03T09:08:52.123734+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "39a1bd71-3da9-4670-ab5e-85592dda02a0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37811", "type": "seen", "source": "https://t.me/cvedetector/24811", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-37811 - \"Qualcomm Chipidea USB Driver Null Pointer Dereference\"\", \n \"Content\": \"CVE ID : CVE-2025-37811 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nusb: chipidea: ci_hdrc_imx: fix usbmisc handling \n \nusbmisc is an optional device property so it is totally valid for the \ncorresponding data->usbmisc_data to have a NULL value. \n \nCheck that before dereferencing the pointer. \n \nFound by Linux Verification Center (linuxtesting.org) with Svace static \nanalysis tool. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"08 May 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:46.000000Z"} 2025-05-08T11:45:46+00:00 https://vulnerability.circl.lu/sighting/66b76c01-e516-4954-9ced-3000f64c7bc3/export 2026-09-03T09:08:52.126787+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "66b76c01-e516-4954-9ced-3000f64c7bc3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37812", "type": "seen", "source": "https://t.me/cvedetector/24810", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-37812 - Linux Kernel USB cdns3 NCM Gadget Deadlock\", \n \"Content\": \"CVE ID : CVE-2025-37812 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nusb: cdns3: Fix deadlock when using NCM gadget \n \nThe cdns3 driver has the same NCM deadlock as fixed in cdnsp by commit \n58f2fcb3a845 (\"usb: cdnsp: Fix deadlock issue during using NCM gadget\"). \n \nUnder PREEMPT_RT the deadlock can be readily triggered by heavy network \ntraffic, for example using \"iperf --bidir\" over NCM ethernet link. \n \nThe deadlock occurs because the threaded interrupt handler gets \npreempted by a softirq, but both are protected by the same spinlock. \nPrevent deadlock by disabling softirq during threaded irq handler. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"08 May 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:45.000000Z"} 2025-05-08T11:45:45+00:00 https://vulnerability.circl.lu/sighting/2ebe0f7a-be4a-4698-982a-1f4e74932c02/export 2026-09-03T09:08:52.127020+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "2ebe0f7a-be4a-4698-982a-1f4e74932c02", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37819", "type": "published-proof-of-concept", "source": "https://t.me/cvedetector/24806", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-37819 - \"Linux Kernel GICv2m Use After Free Vulnerability in irqchip\"\", \n \"Content\": \"CVE ID : CVE-2025-37819 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nirqchip/gic-v2m: Prevent use after free of gicv2m_get_fwnode() \n \nWith ACPI in place, gicv2m_get_fwnode() is registered with the pci \nsubsystem as pci_msi_get_fwnode_cb(), which may get invoked at runtime \nduring a PCI host bridge probe. But, the call back is wrongly marked as \n__init, causing it to be freed, while being registered with the PCI \nsubsystem and could trigger: \n \n Unable to handle kernel paging request at virtual address ffff8000816c0400 \n gicv2m_get_fwnode+0x0/0x58 (P) \n pci_set_bus_msi_domain+0x74/0x88 \n pci_register_host_bridge+0x194/0x548 \n \nThis is easily reproducible on a Juno board with ACPI boot. \n \nRetain the function for later use. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"08 May 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:06.000000Z"} 2025-05-08T11:45:06+00:00 https://vulnerability.circl.lu/sighting/d9a4f55f-c614-4b9d-b35d-0d72abca093a/export 2026-09-03T09:08:52.127179+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "d9a4f55f-c614-4b9d-b35d-0d72abca093a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37818", "type": "seen", "source": "https://t.me/cvedetector/24804", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-37818 - LoongArch Linux Kernel Invalid PMD Pointer Dereference Vulnerability\", \n \"Content\": \"CVE ID : CVE-2025-37818 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nLoongArch: Return NULL from huge_pte_offset() for invalid PMD \n \nLoongArch's huge_pte_offset() currently returns a pointer to a PMD slot \neven if the underlying entry points to invalid_pte_table (indicating no \nmapping). Callers like smaps_hugetlb_range() fetch this invalid entry \nvalue (the address of invalid_pte_table) via this pointer. \n \nThe generic is_swap_pte() check then incorrectly identifies this address \nas a swap entry on LoongArch, because it satisfies the \"!pte_present() \n&& !pte_none()\" conditions. This misinterpretation, combined with a \ncoincidental match by is_migration_entry() on the address bits, leads to \nkernel crashes in pfn_swap_entry_to_page(). \n \nFix this at the architecture level by modifying huge_pte_offset() to \ncheck the PMD entry's content using pmd_none() before returning. If the \nentry is invalid (i.e., it points to invalid_pte_table), return NULL \ninstead of the pointer to the slot. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"08 May 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:01.000000Z"} 2025-05-08T11:45:01+00:00 https://vulnerability.circl.lu/sighting/64a63007-45d7-4d68-87fe-8a79c963d940/export 2026-09-03T09:08:52.127325+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "64a63007-45d7-4d68-87fe-8a79c963d940", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37817", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqr33wi2l", "content": "", "creation_timestamp": "2025-05-08T08:31:37.027797Z"} 2025-05-08T08:31:37.027797+00:00 https://vulnerability.circl.lu/sighting/50f3119d-ad6d-4495-94e7-36602beb4076/export 2026-09-03T09:08:52.127466+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "50f3119d-ad6d-4495-94e7-36602beb4076", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37819", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqqxfmz2r", "content": "", "creation_timestamp": "2025-05-08T08:31:36.489652Z"} 2025-05-08T08:31:36.489652+00:00 https://vulnerability.circl.lu/sighting/1c842eb0-8a1d-4112-ac19-c5fb580b3b53/export 2026-09-03T09:08:52.127584+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "1c842eb0-8a1d-4112-ac19-c5fb580b3b53", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37818", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqqtvxp2h", "content": "", "creation_timestamp": "2025-05-08T08:31:35.709763Z"} 2025-05-08T08:31:35.709763+00:00 https://vulnerability.circl.lu/sighting/2a4d87af-19cc-472a-a693-a220d89af0b9/export 2026-09-03T09:08:52.127692+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "2a4d87af-19cc-472a-a693-a220d89af0b9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37816", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3loniqqkbaj2e", "content": "", "creation_timestamp": "2025-05-08T08:31:35.135172Z"} 2025-05-08T08:31:35.135172+00:00 https://vulnerability.circl.lu/sighting/d3896b10-c5be-4e06-90ea-24ddb2d03400/export 2026-09-03T09:08:52.127796+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "d3896b10-c5be-4e06-90ea-24ddb2d03400", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37812", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15496", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37812\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: Fix deadlock when using NCM gadget\n\nThe cdns3 driver has the same NCM deadlock as fixed in cdnsp by commit\n58f2fcb3a845 (\"usb: cdnsp: Fix deadlock issue during using NCM gadget\").\n\nUnder PREEMPT_RT the deadlock can be readily triggered by heavy network\ntraffic, for example using \"iperf --bidir\" over NCM ethernet link.\n\nThe deadlock occurs because the threaded interrupt handler gets\npreempted by a softirq, but both are protected by the same spinlock.\nPrevent deadlock by disabling softirq during threaded irq handler.\n\ud83d\udccf Published: 2025-05-08T06:26:09.355Z\n\ud83d\udccf Modified: 2025-05-08T06:26:09.355Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/eebfb64c624fc738b669100173344fb441c5e719\n2. https://git.kernel.org/stable/c/59a760e4796a3cd88d8b9d7706e0a638de677751\n3. https://git.kernel.org/stable/c/b96239582531775f2fdcb14de29bdb6870fd4c8c\n4. https://git.kernel.org/stable/c/c27db84ed44e50ff90d9e3a2a25fae2e0a0fa015\n5. https://git.kernel.org/stable/c/48a62deb857f0694f611949015e70ad194d97159\n6. https://git.kernel.org/stable/c/74cd6e408a4c010e404832f0e4609d29bf1d0c41\n7. https://git.kernel.org/stable/c/09e90a9689a4aac7a2f726dc2aa472b0b37937b7\n8. https://git.kernel.org/stable/c/a1059896f2bfdcebcdc7153c3be2307ea319501f", "creation_timestamp": "2025-05-08T07:23:24.000000Z"} 2025-05-08T07:23:24+00:00 https://vulnerability.circl.lu/sighting/7edfa7ef-4243-4383-ab90-b19690f4af72/export 2026-09-03T09:08:52.127956+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "7edfa7ef-4243-4383-ab90-b19690f4af72", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37813", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15495", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37813\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nusb: xhci: Fix invalid pointer dereference in Etron workaround\n\nThis check is performed before prepare_transfer() and prepare_ring(), so\nenqueue can already point at the final link TRB of a segment. And indeed\nit will, some 0.4% of times this code is called.\n\nThen enqueue + 1 is an invalid pointer. It will crash the kernel right\naway or load some junk which may look like a link TRB and cause the real\nlink TRB to be replaced with a NOOP. This wouldn't end well.\n\nUse a functionally equivalent test which doesn't dereference the pointer\nand always gives correct result.\n\nSomething has crashed my machine twice in recent days while playing with\nan Etron HC, and a control transfer stress test ran for confirmation has\njust crashed it again. The same test passes with this patch applied.\n\ud83d\udccf Published: 2025-05-08T06:26:10.000Z\n\ud83d\udccf Modified: 2025-05-08T06:26:10.000Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/142273a49f2c315eabdbdf5a71c15e479b75ca91\n2. https://git.kernel.org/stable/c/bce3055b08e303e28a8751f6073066f5c33a0744\n3. https://git.kernel.org/stable/c/0624e29c595b05e7a0e6d1c368f0a05799928e30\n4. https://git.kernel.org/stable/c/1ea050da5562af9b930d17cbbe9632d30f5df43a", "creation_timestamp": "2025-05-08T07:23:23.000000Z"} 2025-05-08T07:23:23+00:00