{"vulnerability": "CVE-2025-3788", "sightings": [{"uuid": "6e7813ff-ca53-4aa6-8222-405cdd58ebf4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37884", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "7395e48d-7db7-4680-a3d7-7806945711d4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37880", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "96af89b2-7f3a-48a9-adf4-982853eac38a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37884", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "4073bf82-6407-4098-8592-ca9e6eb9470b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37880", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15693", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37880\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\num: work around sched_yield not yielding in time-travel mode\n\nsched_yield by a userspace may not actually cause scheduling in\ntime-travel mode as no time has passed. In the case seen it appears to\nbe a badly implemented userspace spinlock in ASAN. Unfortunately, with\ntime-travel it causes an extreme slowdown or even deadlock depending on\nthe kernel configuration (CONFIG_UML_MAX_USERSPACE_ITERATIONS).\n\nWork around it by accounting time to the process whenever it executes a\nsched_yield syscall.\n\ud83d\udccf Published: 2025-05-09T06:45:44.117Z\n\ud83d\udccf Modified: 2025-05-09T06:45:44.117Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/da780c4a075ba2deb05ae29f0af4a990578c7901\n2. https://git.kernel.org/stable/c/990ddc65173776f1e01e7135d8c1fd5f8fd4d5d2\n3. https://git.kernel.org/stable/c/887c5c12e80c8424bd471122d2e8b6b462e12874", "creation_timestamp": "2025-05-09T07:25:38.000000Z"}, {"uuid": "32b90a80-c26a-4cc5-a8b1-a282f25a5a1e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37881", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15692", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37881\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: aspeed: Add NULL pointer check in ast_vhub_init_dev()\n\nThe variable d->name, returned by devm_kasprintf(), could be NULL.\nA pointer check is added to prevent potential NULL pointer dereference.\nThis is similar to the fix in commit 3027e7b15b02\n(\"ice: Fix some null pointer dereference issues in ice_ptp.c\").\n\nThis issue is found by our static analysis tool\n\ud83d\udccf Published: 2025-05-09T06:45:45.205Z\n\ud83d\udccf Modified: 2025-05-09T06:45:45.205Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/a777ccfb9ba8d43f745e41b69ba39d4a506a081e\n2. https://git.kernel.org/stable/c/c8d4faf452a627f9b09c3a5c366133a19e5b7a28\n3. https://git.kernel.org/stable/c/d26a6093d52904cacdbb75424c323c19b443a890\n4. https://git.kernel.org/stable/c/36d68151712e525450f0fbb3045e7110f0d9b610\n5. https://git.kernel.org/stable/c/cfa7984f69359761b07a7831c1258c0fde1e0389\n6. https://git.kernel.org/stable/c/052fb65335befeae8500e88d69ea022266baaf6d\n7. https://git.kernel.org/stable/c/61006ca381b4d65d2b8ca695ea8da1ce18d6dee3\n8. https://git.kernel.org/stable/c/8c75f3e6a433d92084ad4e78b029ae680865420f", "creation_timestamp": "2025-05-09T07:25:35.000000Z"}, {"uuid": "1dbd66f3-fdbd-4607-95d2-98211f424337", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37886", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15687", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37886\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\npds_core: make wait_context part of q_info\n\nMake the wait_context a full part of the q_info struct rather\nthan a stack variable that goes away after pdsc_adminq_post()\nis done so that the context is still available after the wait\nloop has given up.\n\nThere was a case where a slow development firmware caused\nthe adminq request to time out, but then later the FW finally\nfinished the request and sent the interrupt.  The handler tried\nto complete_all() the completion context that had been created\non the stack in pdsc_adminq_post() but no longer existed.\nThis caused bad pointer usage, kernel crashes, and much wailing\nand gnashing of teeth.\n\ud83d\udccf Published: 2025-05-09T06:45:48.810Z\n\ud83d\udccf Modified: 2025-05-09T06:45:48.810Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/1d7c4b2b0bbfb09b55b2dc0e2355d7936bf89381\n2. https://git.kernel.org/stable/c/66d7702b42ffdf0dce4808626088268a4e905ca6\n3. https://git.kernel.org/stable/c/520f012fe75fb8efc9f16a57ef929a7a2115d892\n4. https://git.kernel.org/stable/c/3f77c3dfffc7063428b100c4945ca2a7a8680380", "creation_timestamp": "2025-05-09T07:25:28.000000Z"}, {"uuid": "ffa31f00-a989-47fb-aa25-bc20be106166", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37887", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15686", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37887\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\npds_core: handle unsupported PDS_CORE_CMD_FW_CONTROL result\n\nIf the FW doesn't support the PDS_CORE_CMD_FW_CONTROL command\nthe driver might at the least print garbage and at the worst\ncrash when the user runs the \"devlink dev info\" devlink command.\n\nThis happens because the stack variable fw_list is not 0\ninitialized which results in fw_list.num_fw_slots being a\ngarbage value from the stack.  Then the driver tries to access\nfw_list.fw_names[i] with i >= ARRAY_SIZE and runs off the end\nof the array.\n\nFix this by initializing the fw_list and by not failing\ncompletely if the devcmd fails because other useful information\nis printed via devlink dev info even if the devcmd fails.\n\ud83d\udccf Published: 2025-05-09T06:45:49.492Z\n\ud83d\udccf Modified: 2025-05-09T06:45:49.492Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/cdd784c96fe2e5edbf0ed9b3e96fe776e8092385\n2. https://git.kernel.org/stable/c/6702f5c6b22deaa95bf84f526148174a160a02cb\n3. https://git.kernel.org/stable/c/12a4651a80dbe4589a84e26785fbbe1ed4d043b7\n4. https://git.kernel.org/stable/c/2567daad69cd1107fc0ec29b1615f110d7cf7385", "creation_timestamp": "2025-05-09T07:25:27.000000Z"}, {"uuid": "56c414d7-0b20-4a27-b99c-a6ad549737e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37888", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15685", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37888\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Fix null-ptr-deref in mlx5_create_{inner_,}ttc_table()\n\nAdd NULL check for mlx5_get_flow_namespace() returns in\nmlx5_create_inner_ttc_table() and mlx5_create_ttc_table() to prevent\nNULL pointer dereference.\n\ud83d\udccf Published: 2025-05-09T06:45:50.128Z\n\ud83d\udccf Modified: 2025-05-09T06:45:50.128Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/0b682680b12b08cd62b113ea92b2938195de1dfe\n2. https://git.kernel.org/stable/c/ecd9d2647ddb4f42a121de648e48659ae1856c39\n3. https://git.kernel.org/stable/c/91037037ee3d611ce17f39d75f79c7de394b122a", "creation_timestamp": "2025-05-09T07:25:25.000000Z"}, {"uuid": "69fc8a5a-03fb-48e4-8352-f524bde3c6b2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37889", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15684", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37889\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nPCI/MSI: Handle the NOMASK flag correctly for all PCI/MSI backends\n\nThe conversion of the XEN specific global variable pci_msi_ignore_mask to a\nMSI domain flag, missed the facts that:\n\n    1) Legacy architectures do not provide a interrupt domain\n    2) Parent MSI domains do not necessarily have a domain info attached\n   \nBoth cases result in an unconditional NULL pointer dereference. This was\nunfortunatly missed in review and testing revealed it late.\n\nCure this by using the existing pci_msi_domain_supports() helper, which\nhandles all possible cases correctly.\n\ud83d\udccf Published: 2025-05-09T06:45:50.868Z\n\ud83d\udccf Modified: 2025-05-09T06:45:50.868Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/46d357520934eef99fa121889f8ebbf46a6eddb8\n2. https://git.kernel.org/stable/c/2e3ad60b8f72a95e3a32ddd9d70ea129aa3fcfb7\n3. https://git.kernel.org/stable/c/3ece3e8e5976c49c3f887e5923f998eabd54ff40", "creation_timestamp": "2025-05-09T07:25:24.000000Z"}, {"uuid": "cc1445ee-1885-4bd0-a0a1-cd01abfc8283", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37885", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15688", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37885\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Reset IRTE to host control if *new* route isn't postable\n\nRestore an IRTE back to host control (remapped or posted MSI mode) if the\n*new* GSI route prevents posting the IRQ directly to a vCPU, regardless of\nthe GSI routing type.  Updating the IRTE if and only if the new GSI is an\nMSI results in KVM leaving an IRTE posting to a vCPU.\n\nThe dangling IRTE can result in interrupts being incorrectly delivered to\nthe guest, and in the worst case scenario can result in use-after-free,\ne.g. if the VM is torn down, but the underlying host IRQ isn't freed.\n\ud83d\udccf Published: 2025-05-09T06:45:48.150Z\n\ud83d\udccf Modified: 2025-05-09T06:45:48.150Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/e5f2dee9f7fcd2ff4b97869f3c66a0d89c167769\n2. https://git.kernel.org/stable/c/116c7d35b8f72eac383b9fd371d7c1a8ffc2968b\n3. https://git.kernel.org/stable/c/023816bd5fa46fab94d1e7917fe131b79ed1fb41\n4. https://git.kernel.org/stable/c/3481fd96d801715942b6f69fe251133128156f30\n5. https://git.kernel.org/stable/c/b5de7ac74f69603ad803c524b840bffd36368fc3\n6. https://git.kernel.org/stable/c/3066ec21d1a33896125747f68638725f456308db\n7. https://git.kernel.org/stable/c/9bcac97dc42d2f4da8229d18feb0fe2b1ce523a2", "creation_timestamp": "2025-05-09T07:25:29.000000Z"}, {"uuid": "7c25face-5398-419b-bb7c-20aa0a12bc14", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37882", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15691", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37882\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 isochronous Ring Underrun/Overrun event handling\n\nThe TRB pointer of these events points at enqueue at the time of error\noccurrence on xHCI 1.1+ HCs or it's NULL on older ones. By the time we\nare handling the event, a new TD may be queued at this ring position.\n\nI can trigger this race by rising interrupt moderation to increase IRQ\nhandling delay. Similar delay may occur naturally due to system load.\n\nIf this ever happens after a Missed Service Error, missed TDs will be\nskipped and the new TD processed as if it matched the event. It could\nbe given back prematurely, risking data loss or buffer UAF by the xHC.\n\nDon't complete TDs on xrun events and don't warn if queued TDs don't\nmatch the event's TRB pointer, which can be NULL or a link/no-op TRB.\nDon't warn if there are no queued TDs at all.\n\nNow that it's safe, also handle xrun events if the skip flag is clear.\nThis ensures completion of any TD stuck in 'error mid TD' state right\nbefore the xrun event, which could happen if a driver submits a finite\nnumber of URBs to a buggy HC and then an error occurs on the last TD.\n\ud83d\udccf Published: 2025-05-09T06:45:45.936Z\n\ud83d\udccf Modified: 2025-05-09T06:45:45.936Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/16a7a8e6c47fea5c847beb696c8c21a7a44c1915\n2. https://git.kernel.org/stable/c/39a080a2925c81b0f1da0add44722ef2b78e5454\n3. https://git.kernel.org/stable/c/906dec15b9b321b546fd31a3c99ffc13724c7af4", "creation_timestamp": "2025-05-09T07:25:31.000000Z"}, {"uuid": "1f2a8268-7736-47b3-82e9-076fd7ce7ffd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37883", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15690", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37883\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ns390/sclp: Add check for get_zeroed_page()\n\nAdd check for the return value of get_zeroed_page() in\nsclp_console_init() to prevent null pointer dereference.\nFurthermore, to solve the memory leak caused by the loop\nallocation, add a free helper to do the free job.\n\ud83d\udccf Published: 2025-05-09T06:45:46.716Z\n\ud83d\udccf Modified: 2025-05-09T06:45:46.716Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/e1e00dc45648125ef7cb87ebc3b581ac224e7b39\n2. https://git.kernel.org/stable/c/397254706eba9d8f99fd237feede7ab3169a7f9a\n3. https://git.kernel.org/stable/c/28e5a867aa542e369e211c2baba7044228809a99\n4. https://git.kernel.org/stable/c/3b3aa72636a6205933609ec274a8747720c1ee3f\n5. https://git.kernel.org/stable/c/f69f8a93aacf6e99af7b1cc992d8ca2cc07b96fb\n6. https://git.kernel.org/stable/c/3db42c75a921854a99db0a2775814fef97415bac", "creation_timestamp": "2025-05-09T07:25:30.000000Z"}, {"uuid": "597f713b-0c1c-4f4b-a594-09aff167b268", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37884", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15689", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37884\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix deadlock between rcu_tasks_trace and event_mutex.\n\nFix the following deadlock:\nCPU A\n_free_event()\n  perf_kprobe_destroy()\n    mutex_lock(&event_mutex)\n      perf_trace_event_unreg()\n        synchronize_rcu_tasks_trace()\n\nThere are several paths where _free_event() grabs event_mutex\nand calls sync_rcu_tasks_trace. Above is one such case.\n\nCPU B\nbpf_prog_test_run_syscall()\n  rcu_read_lock_trace()\n    bpf_prog_run_pin_on_cpu()\n      bpf_prog_load()\n        bpf_tracing_func_proto()\n          trace_set_clr_event()\n            mutex_lock(&event_mutex)\n\nDelegate trace_set_clr_event() to workqueue to avoid\nsuch lock dependency.\n\ud83d\udccf Published: 2025-05-09T06:45:47.462Z\n\ud83d\udccf Modified: 2025-05-09T06:45:47.462Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/255cbc9db7067a83713fd2f4b31034ddd266549a\n2. https://git.kernel.org/stable/c/b5a528a34e1f613565115a7a6016862ccbfcb9ac\n3. https://git.kernel.org/stable/c/c5c833f6375f8ecf9254dd27946c927c7d645421\n4. https://git.kernel.org/stable/c/45286680b385f2592db3003554872388dee66d68\n5. https://git.kernel.org/stable/c/4580f4e0ebdf8dc8d506ae926b88510395a0c1d1", "creation_timestamp": "2025-05-09T07:25:29.000000Z"}, {"uuid": "bc7d4de7-e38d-438d-be8d-24c18238995d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37881", "type": "seen", "source": "https://t.me/cvedetector/24929", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37881 - Aspeed USB Gadget NULL Pointer Dereference\", \n  \"Content\": \"CVE ID : CVE-2025-37881 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nusb: gadget: aspeed: Add NULL pointer check in ast_vhub_init_dev()  \n  \nThe variable d->name, returned by devm_kasprintf(), could be NULL.  \nA pointer check is added to prevent potential NULL pointer dereference.  \nThis is similar to the fix in commit 3027e7b15b02  \n(\"ice: Fix some null pointer dereference issues in ice_ptp.c\").  \n  \nThis issue is found by our static analysis tool \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:21:57.000000Z"}, {"uuid": "072ea304-8c69-4558-939e-3b52cf78ab5f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37888", "type": "seen", "source": "https://t.me/cvedetector/24922", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37888 - Intel Mellanox Linux Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37888 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet/mlx5: Fix null-ptr-deref in mlx5_create_{inner_,}ttc_table()  \n  \nAdd NULL check for mlx5_get_flow_namespace() returns in  \nmlx5_create_inner_ttc_table() and mlx5_create_ttc_table() to prevent  \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\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:21:46.000000Z"}, {"uuid": "17f5198f-0053-4906-9f1d-2df90a02c08e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-3788", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3ln3iuub3jhe2", "content": "", "creation_timestamp": "2025-04-18T11:26:52.674543Z"}, {"uuid": "93c2cdff-39a8-4f77-b436-f690cd9d34c8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-3788", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln42fqcy2c2b", "content": "", "creation_timestamp": "2025-04-18T16:34:31.028132Z"}, {"uuid": "2080aad3-8dbb-4cd3-a8f9-31a265331677", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37889", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lotadoxxk232", "content": "", "creation_timestamp": "2025-05-10T15:17:35.831710Z"}, {"uuid": "3222864e-9edc-4daf-bbe3-8d685d36041f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3mgff4w63em24", "content": "", "creation_timestamp": "2026-03-06T13:10:10.047966Z"}, {"uuid": "908f2f50-1f68-4714-8129-ee7a7a5a30bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3mfccsjc2s322", "content": "", "creation_timestamp": "2026-02-20T14:25:22.254685Z"}, {"uuid": "b68f7a1d-bd63-4404-9972-505e97932462", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "cb3b1674-8b64-44bb-ac19-e0ced55abf50", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37883", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "1770de2d-7218-4b9a-8ebc-8346c39c105a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-3788", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12415", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-3788\n\ud83d\udd25 CVSS Score: 5.1 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: A vulnerability was found in baseweb JSite 1.0. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /a/sys/user/save. The manipulation of the argument Name leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.\n\ud83d\udccf Published: 2025-04-18T10:00:12.652Z\n\ud83d\udccf Modified: 2025-04-18T10:00:12.652Z\n\ud83d\udd17 References:\n1. https://vuldb.com/?id.305611\n2. https://vuldb.com/?ctiid.305611\n3. https://vuldb.com/?submit.554565\n4. https://github.com/caigo8/CVE-md/blob/main/JSite/XSS1.md", "creation_timestamp": "2025-04-18T10:59:16.000000Z"}, {"uuid": "c2af9a8c-60a0-49e0-9189-ab7ff23df327", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37884", "type": "seen", "source": "https://t.me/cvedetector/24933", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37884 - Linux Kernel BPF Event Mutex Deadlock\", \n  \"Content\": \"CVE ID : CVE-2025-37884 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: Fix deadlock between rcu_tasks_trace and event_mutex.  \n  \nFix the following deadlock:  \nCPU A  \n_free_event()  \n  perf_kprobe_destroy()  \n    mutex_lock(&event_mutex)  \n      perf_trace_event_unreg()  \n        synchronize_rcu_tasks_trace()  \n  \nThere are several paths where _free_event() grabs event_mutex  \nand calls sync_rcu_tasks_trace. Above is one such case.  \n  \nCPU B  \nbpf_prog_test_run_syscall()  \n  rcu_read_lock_trace()  \n    bpf_prog_run_pin_on_cpu()  \n      bpf_prog_load()  \n        bpf_tracing_func_proto()  \n          trace_set_clr_event()  \n            mutex_lock(&event_mutex)  \n  \nDelegate trace_set_clr_event() to workqueue to avoid  \nsuch lock dependency. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:22:00.000000Z"}, {"uuid": "539dedd4-481f-45f2-8f9a-36ba821150f3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://t.me/cvedetector/24931", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37882 - Linux Kernel USB xHCI Isochronous Ring Handling Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37882 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nusb: xhci: Fix isochronous Ring Underrun/Overrun event handling  \n  \nThe TRB pointer of these events points at enqueue at the time of error  \noccurrence on xHCI 1.1+ HCs or it's NULL on older ones. By the time we  \nare handling the event, a new TD may be queued at this ring position.  \n  \nI can trigger this race by rising interrupt moderation to increase IRQ  \nhandling delay. Similar delay may occur naturally due to system load.  \n  \nIf this ever happens after a Missed Service Error, missed TDs will be  \nskipped and the new TD processed as if it matched the event. It could  \nbe given back prematurely, risking data loss or buffer UAF by the xHC.  \n  \nDon't complete TDs on xrun events and don't warn if queued TDs don't  \nmatch the event's TRB pointer, which can be NULL or a link/no-op TRB.  \nDon't warn if there are no queued TDs at all.  \n  \nNow that it's safe, also handle xrun events if the skip flag is clear.  \nThis ensures completion of any TD stuck in 'error mid TD' state right  \nbefore the xrun event, which could happen if a driver submits a finite  \nnumber of URBs to a buggy HC and then an error occurs on the last TD. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:21:59.000000Z"}, {"uuid": "fa2f893c-75aa-4f5e-8c40-5b4fd460759e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37880", "type": "seen", "source": "https://t.me/cvedetector/24930", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37880 - Linux um Time-Travel Scheduling Vulnerability (Deadlock)\", \n  \"Content\": \"CVE ID : CVE-2025-37880 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \num: work around sched_yield not yielding in time-travel mode  \n  \nsched_yield by a userspace may not actually cause scheduling in  \ntime-travel mode as no time has passed. In the case seen it appears to  \nbe a badly implemented userspace spinlock in ASAN. Unfortunately, with  \ntime-travel it causes an extreme slowdown or even deadlock depending on  \nthe kernel configuration (CONFIG_UML_MAX_USERSPACE_ITERATIONS).  \n  \nWork around it by accounting time to the process whenever it executes a  \nsched_yield syscall. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:21:58.000000Z"}, {"uuid": "4f091a1f-9d56-4f67-bb62-996f984d8990", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37886", "type": "seen", "source": "https://t.me/cvedetector/24935", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37886 - Linux Kernel PDS Core Use-After-Free Buffer Overflow\", \n  \"Content\": \"CVE ID : CVE-2025-37886 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \npds_core: make wait_context part of q_info  \n  \nMake the wait_context a full part of the q_info struct rather  \nthan a stack variable that goes away after pdsc_adminq_post()  \nis done so that the context is still available after the wait  \nloop has given up.  \n  \nThere was a case where a slow development firmware caused  \nthe adminq request to time out, but then later the FW finally  \nfinished the request and sent the interrupt.  The handler tried  \nto complete_all() the completion context that had been created  \non the stack in pdsc_adminq_post() but no longer existed.  \nThis caused bad pointer usage, kernel crashes, and much wailing  \nand gnashing of teeth. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:22:05.000000Z"}, {"uuid": "d217279a-8006-4035-b529-8d9878d776d5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37883", "type": "seen", "source": "https://t.me/cvedetector/24936", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37883 - IBM s390 Linux Kernel Null Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37883 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ns390/sclp: Add check for get_zeroed_page()  \n  \nAdd check for the return value of get_zeroed_page() in  \nsclp_console_init() to prevent null pointer dereference.  \nFurthermore, to solve the memory leak caused by the loop  \nallocation, add a free helper to do the free job. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:22:06.000000Z"}, {"uuid": "bd7274aa-f67a-4218-b09a-a29839b6428a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37885", "type": "seen", "source": "https://t.me/cvedetector/24934", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37885 - KVM Linux Kernel MSI Route Handling Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37885 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nKVM: x86: Reset IRTE to host control if *new* route isn't postable  \n  \nRestore an IRTE back to host control (remapped or posted MSI mode) if the  \n*new* GSI route prevents posting the IRQ directly to a vCPU, regardless of  \nthe GSI routing type.  Updating the IRTE if and only if the new GSI is an  \nMSI results in KVM leaving an IRTE posting to a vCPU.  \n  \nThe dangling IRTE can result in interrupts being incorrectly delivered to  \nthe guest, and in the worst case scenario can result in use-after-free,  \ne.g. if the VM is torn down, but the underlying host IRQ isn't freed. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:22:04.000000Z"}, {"uuid": "3756b69f-291b-44bb-8ffb-c90716a7730b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37887", "type": "seen", "source": "https://t.me/cvedetector/24927", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37887 - Linux Kernel PDS_CORE Devlink Command Buffer Overflow\", \n  \"Content\": \"CVE ID : CVE-2025-37887 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \npds_core: handle unsupported PDS_CORE_CMD_FW_CONTROL result  \n  \nIf the FW doesn't support the PDS_CORE_CMD_FW_CONTROL command  \nthe driver might at the least print garbage and at the worst  \ncrash when the user runs the \"devlink dev info\" devlink command.  \n  \nThis happens because the stack variable fw_list is not 0  \ninitialized which results in fw_list.num_fw_slots being a  \ngarbage value from the stack.  Then the driver tries to access  \nfw_list.fw_names[i] with i >= ARRAY_SIZE and runs off the end  \nof the array.  \n  \nFix this by initializing the fw_list and by not failing  \ncompletely if the devcmd fails because other useful information  \nis printed via devlink dev info even if the devcmd fails. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:21:53.000000Z"}, {"uuid": "01f2ea70-7f5e-4091-8262-6f3d64018370", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37889", "type": "seen", "source": "https://t.me/cvedetector/24923", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37889 - XEN PCI MSI NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37889 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nPCI/MSI: Handle the NOMASK flag correctly for all PCI/MSI backends  \n  \nThe conversion of the XEN specific global variable pci_msi_ignore_mask to a  \nMSI domain flag, missed the facts that:  \n  \n    1) Legacy architectures do not provide a interrupt domain  \n    2) Parent MSI domains do not necessarily have a domain info attached  \n     \nBoth cases result in an unconditional NULL pointer dereference. This was  \nunfortunatly missed in review and testing revealed it late.  \n  \nCure this by using the existing pci_msi_domain_supports() helper, which  \nhandles all possible cases correctly. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:21:47.000000Z"}, {"uuid": "e8105e8b-bcbc-4168-8923-d23bcd23b62d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0290/", "content": "", "creation_timestamp": "2026-03-13T00:00:00.000000Z"}, {"uuid": "e3b080dd-c2d7-4536-9482-69e99d644ade", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37885", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "aaacd0ee-0465-4b71-b7bb-d8c1ae6f1c9a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "69a249d1-0324-4745-ad8d-b6e45adc386d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37880", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "915dbe58-0de9-4fe5-b866-096952fffa32", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37881", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7ybev42t", "content": "", "creation_timestamp": "2025-05-09T08:31:46.367216Z"}, {"uuid": "13934da7-3d5b-4881-a0b5-1e8a8185640b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37880", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7yf3ud2l", "content": "", "creation_timestamp": "2025-05-09T08:31:46.968117Z"}, {"uuid": "7888c6a0-60ef-4c71-bcdc-9949fa69a92f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37884", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7yinkc2h", "content": "", "creation_timestamp": "2025-05-09T08:31:47.523161Z"}, {"uuid": "896beb79-c60c-43b7-a798-9bcf9ec52c89", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37889", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7ylxro2h", "content": "", "creation_timestamp": "2025-05-09T08:31:48.116554Z"}, {"uuid": "73f22829-0204-400d-8ab0-f8a9412da9f8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37888", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7ypn6z24", "content": "", "creation_timestamp": "2025-05-09T08:31:48.677375Z"}, {"uuid": "10d3dcd9-a03a-473b-a0f1-25a73bac7195", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7ytbko2n", "content": "", "creation_timestamp": "2025-05-09T08:31:49.242381Z"}, {"uuid": "a09b991b-56de-4ea8-89ed-fd6a26443c96", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37885", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7ywwmq2j", "content": "", "creation_timestamp": "2025-05-09T08:31:49.822742Z"}, {"uuid": "6c1b1857-05b3-4b72-bed1-580237353b84", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37887", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7z2a7o2n", "content": "", "creation_timestamp": "2025-05-09T08:31:50.380693Z"}, {"uuid": "025fbbea-b704-4f27-b8f7-1c0bdba8cb1e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37883", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7z5kau2t", "content": "", "creation_timestamp": "2025-05-09T08:31:50.948385Z"}, {"uuid": "6983e3ce-d2e0-4b03-b395-28276de2c925", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37886", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lopz7zaxnx2e", "content": "", "creation_timestamp": "2025-05-09T08:31:51.495278Z"}, {"uuid": "80534d9b-571b-4d0f-9eb8-83f2ec41510e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37882", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwp33ml4e2", "content": "", "creation_timestamp": "2025-05-09T09:21:34.242706Z"}, {"uuid": "2008ace9-b40d-4dd1-8524-1c5fee60157b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37884", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwp5fhbcx2", "content": "", "creation_timestamp": "2025-05-09T09:21:35.004094Z"}, {"uuid": "b0c0cdd1-7ae5-4933-9657-151f1682dba5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37889", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwpj3tvyu2", "content": "", "creation_timestamp": "2025-05-09T09:21:37.069304Z"}, {"uuid": "4f7a1ccf-e8e0-4e0d-b46c-d9a75217cf4a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37883", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwpegkkku2", "content": "", "creation_timestamp": "2025-05-09T09:21:37.715427Z"}, {"uuid": "2ae9db8f-2d0d-4c4b-bbeb-c1673ae1502b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37888", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwpsfsykk2", "content": "", "creation_timestamp": "2025-05-09T09:21:39.557678Z"}, {"uuid": "ac25d93f-6c63-4d6d-847b-297702e611fd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37887", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwq665cle2", "content": "", "creation_timestamp": "2025-05-09T09:21:40.446916Z"}, {"uuid": "a81fa361-cd6e-4f7f-90e8-ad7e0f1f1e8f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37886", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwqddvkzx2", "content": "", "creation_timestamp": "2025-05-09T09:21:41.160449Z"}, {"uuid": "a478a915-0906-4a70-9d3d-783fc4d2dbe9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37885", "type": "seen", "source": "https://bsky.app/profile/linux.activitypub.awakari.com.ap.brid.gy/post/3lopwqiszvvu2", "content": "", "creation_timestamp": "2025-05-09T09:21:42.376739Z"}]}