Windows Subsystem For Linux Wsl2
Monthly
Local privilege escalation in Microsoft's Windows Subsystem for Linux (WSL2) allows a low-privileged authenticated user on the Windows host to elevate to higher privileges by triggering a buffer over-read (CWE-126). Microsoft (the reporting vendor) has released a fix via MSRC, and there is no public exploit identified at time of analysis. With a CVSS 3.1 base score of 7.8 and full high impact to confidentiality, integrity and availability, it is a meaningful local EoP but requires prior code-execution access on the machine.
Tampering via a time-of-check time-of-use (TOCTOU) race condition in Windows Subsystem for Linux 2 (WSL2) enables a locally authorized, low-privileged attacker to manipulate file system or resource state between the moment a security check is performed and the moment the resource is actually used. Affected versions run below 2.7.10, and Microsoft has released a fix. No public exploit code has been identified and CISA has not added this to the KEV catalog, but the SSVC framework assesses technical impact as total if the race is won, making the integrity risk significant despite a medium CVSS score.
Local privilege escalation in Microsoft's Windows Subsystem for Linux (WSL2) allows a low-privileged authenticated user on the Windows host to elevate to higher privileges by triggering a buffer over-read (CWE-126). Microsoft (the reporting vendor) has released a fix via MSRC, and there is no public exploit identified at time of analysis. With a CVSS 3.1 base score of 7.8 and full high impact to confidentiality, integrity and availability, it is a meaningful local EoP but requires prior code-execution access on the machine.
Tampering via a time-of-check time-of-use (TOCTOU) race condition in Windows Subsystem for Linux 2 (WSL2) enables a locally authorized, low-privileged attacker to manipulate file system or resource state between the moment a security check is performed and the moment the resource is actually used. Affected versions run below 2.7.10, and Microsoft has released a fix. No public exploit code has been identified and CISA has not added this to the KEV catalog, but the SSVC framework assesses technical impact as total if the race is won, making the integrity risk significant despite a medium CVSS score.