time-travel mode · um: work around sched_yield not yielding
Affects MicrosoftSource GCVE Database
Not known to be exploited.
Data as of 18 Nov 2026, 02:25 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Exploitation evidence
Disclosed: evidence found.
CVE published 2 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Security Response Center Microsoft | Affected
| Fixed in– |
Description
This entry references a workaround related to the sched_yield function not yielding properly in time-travel mode. No detailed vulnerability description, impact, or exploit information is provided. The affected versions are Microsoft product versions 2.0 and 3.0. No CVSS score or patch information is available.