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