{"vulnerability": "CVE-2025-37886", "sightings": [{"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": "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": "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": "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"}]}