{"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"}