Skip to content

Tags: microsoft/WSL

Tags

2.9.9

Toggle 2.9.9's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Skip publishing DCAT script as artifact (#41431)

2.9.8

Toggle 2.9.8's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Poll for the result of operations during MSI installation (#41415)

* Poll for the result of operations during MSI installation

* Cleanup

2.7.12

Toggle 2.7.12's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
[release/2.7] Fix VHD ownership during distribution moves (#41354)

* Fix VHD ownership during distribution moves (#41333)

Run distribution moves under a duplicated caller token whose default owner is the caller's user SID. This keeps cross-volume copies accessible without reopening the destination to rewrite its owner.

Co-authored-by: Ben Hillis <benhill@ntdev.microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* fix build error

* Preserve token owner during move rollback

Save the duplicated caller token's original default owner before normalizing it for a distribution move. Restore that owner before a rollback so cross-volume rollback copies retain the caller token's prior ownership behavior.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Restore VHD owner during move rollback

Capture the source VHD owner before moving it and use that SID as the duplicated token's default owner for a cross-volume rollback. This leaves ownership unchanged when the operation fails.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Request token owner adjustment access for distro moves

MoveDistribution updates the duplicated caller token's default owner before moving a VHD. Request TOKEN_ADJUST_DEFAULT for this operation so SetTokenInformation succeeds on release/2.7.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 36bcfb50-8208-46ef-a5a3-21fb9b57b467

---------

Co-authored-by: Ben Hillis <benhill@ntdev.microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 36bcfb50-8208-46ef-a5a3-21fb9b57b467

2.9.7

Toggle 2.9.7's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Add wsldevicehostproxystub.dll to the list of target to build during …

…release builds (#41317)

2.9.6

Toggle 2.9.6's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Fix unqualified WEX::Logging::Log breaking release builds (#41315)

2.9.5

Toggle 2.9.5's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Restore pipeline logic to push updates to the store by default (#41308)

2.7.11

Toggle 2.7.11's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Backport security fixes to release/2.7 (#41155)

* Bump Microsoft.NETCore.App.Runtime to 10.0.8 (CVE-2026-32175) (#40581)

Fixes Dependabot alerts #24 and #25.

Co-authored-by: Ben Hillis <benhillis@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
(cherry picked from commit 09a8afe)

* Update MSRDC to 1.2.7214 to fix CVE-2026-32157 (#40882)

Bumps Microsoft.RemoteDesktop.Client.MSRDC.SessionHost from 1.2.6676 to
1.2.7214. This closes CVE-2026-32157 (a use-after-free RCE in the Remote
Desktop client, first fixed in 1.2.7099) along with several additional
CVEs shipped in 1.2.7214.

Fixes #40868

Co-authored-by: Ben Hillis <benhill@ntdev.microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
(cherry picked from commit 2a7269e)

* Update .NET runtime to 10.0.9 to fix CVE-2026-45491 (#40883)

Bumps Microsoft.NETCore.App.Runtime.win-x64 and win-arm64 from 10.0.8 to
10.0.9 to address CVE-2026-45491 (.NET tampering vulnerability), reported
by Dependabot. Both runtime packages are bumped together to keep the
.NET runtime version in sync across architectures.

Co-authored-by: Ben Hillis <benhill@ntdev.microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
(cherry picked from commit 73a6afb)

---------

Co-authored-by: Ben Hillis <benhillis@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Ben Hillis <benhill@ntdev.microsoft.com>

2.9.4

Toggle 2.9.4's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Pre-download socat to avoid test failing due to connectivity issues (#…

…41035)

* Pre-download socat to avoid test failings due to connectivity issues

* Cleanup diff

* Apply PR feedback

* Apply PR feedback

* Apply PR feedback

2.9.3

Toggle 2.9.3's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Don't hard-fail the distro validation script when a download fails (#…

…40914)

* Don't hard-fail the distro validation script when a download fails

* Improve error

2.7.10

Toggle 2.7.10's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Fix disk-attach restore TOCTOU by impersonating the mounting user on …

…VHD restore (#40782) (#40907)

* Fix disk-attach restore TOCTOU by impersonating the mounting user on VHD restore

A standard user's live ' wsl --mount --vhd' is already safe from a junction/symlink
swap: the VM access grant runs while impersonating the user, and the SYSTEM-side
AddVhd only succeeds on a file the VM was granted access to, so a swap yields
ACCESS_DENIED rather than disclosure.

The actual gap was disk restore: when the VM is recreated, _LoadDiskMount re-attached
persisted VHDs as SYSTEM (no token), re-resolving a user-controllable path and
reopening the TOCTOU. Because the disk-mount state is stored under the user's SID in a
volatile (per-boot) key, the disk being restored was mounted by this same user in this
same boot, so we can simply pass the user token and let the existing impersonated grant
close the window. Pass-through devices stay SYSTEM (elevation-gated; \\.\PhysicalDriveN
has no reparse surface).

This replaces the earlier handle-pinning/reparse-rejection approach, which also
regressed legitimate symlinked VHDs. Add tests covering a symlinked VHD mounting and
surviving a VM idle-timeout restore.



* Address PR feedback: re-query block device after VM timeout and require symlink creation in mount tests



---------



(cherry picked from commit f0f4b10)

Co-authored-by: Ben Hillis <benhill@ntdev.microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>