The Windows Subsystem for Linux goes open source


Microsoft has officially open-sourced the Windows Subsystem for Linux (WSL), closing the very first issue ever filed on the Microsoft/WSL GitHub repository: “Will this be open source?”

WSL allows developers to run unmodified Linux command-line tools, utilities, and applications directly on Windows, without the overhead of a traditional virtual machine or dual-boot setup.

“Microsoft

WSL architecture overview (Source: Microsoft)

The first version of WSL was introduced in 2016 and implemented as a compatibility layer within the Windows kernel. To improve system call compatibility and performance, WSL 2 was released in 2019, leveraging a real Linux kernel running in a lightweight virtual machine.

As the WSL ecosystem evolved, with support added for GPU acceleration, Linux GUI apps via wslg, and systemd, it became clear that WSL needed to be decoupled from the Windows OS. In 2021, WSL was split into an independent codebase and first shipped to the Microsoft Store as version 0.47.1.

Development continued on this standalone package, culminating in the first stable release in 2022. Windows 11 24H2 was the first Windows build that transitioned users from the built-in WSL to the new WSL package. Microsoft retained wsl.exe in the Windows image to facilitate on-demand downloads of the latest package, easing the transition.

WSL 2.0.0 introduced major improvements such as mirrored networking, DNS tunneling, session 0 support, proxy support, and firewall integration.

“We’ve seen how much the community has contributed to WSL without access to the source code, and we can’t wait to see how WSL will evolve now that the community can make direct code contributions to the project,” said Pierre Boulay from Microsoft.

The following components are still part of the Windows image and are not open sourced at this time:

  • Lxcore.sys, the kernel side driver that powers WSL 1
  • P9rdr.sys and p9np.dll, which runs the “\\wsl.localhost” filesystem redirection (from Windows to Linux)

Developers can now access the WSL source code on GitHub, build it from source, contribute fixes and features, and participate in its ongoing development.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Researchers found one-click RCE in ASUS’s pre-installed software DriverHub

Pierluigi Paganini
May 12, 2025

Expert found two flaws in DriverHub, pre-installed on Asus motherboards, which allows remote code execution via crafted HTTP requests.

Security researcher ‘MrBruh’ discovered two vulnerabilities, tracked as CVE-2025-3462 (CVSS score of 8.4) and CVE-2025-3463 (CVSS score of 9.4), in DriverHub, a driver that is pre-installed on Asus motherboards. A remote attacker can exploit the flaws to gain arbitrary code execution.

Both flaws stem from insufficient validation, allowing misuse of DriverHub features. The company pointed out that the flaws don’t impact laptops and desktops.

DriverHub, a driver updater with no GUI, runs a background process that talks to driverhub.asus.com via RPC on localhost port 53000. Researcher MrBruh found that while it only accepts requests with an origin header set to “driverhub.asus.com,” a flawed wildcard match allowed requests from domains like “driverhub.asus.com.mrbruh.com.” An attacker can exploit this vulnerability to install malicious software.

Researcher MrBruh discovered that Asus DriverHub exposes several local RPC endpoints, including dangerous ones like UpdateApp, which downloads and installs executables with admin rights if signed by Asus. By analyzing JavaScript and decompiled code, he found that a zip file used in driver installs includes an INI setting (SilentInstallRun) that can execute arbitrary commands during silent installs. This opens a path to remote code execution (RCE).

“The files of importance here are the AsusSetup.exeAsusSetup.ini and SilentInstall.cmd. When executing AsusSetup.exe it first reads from AsusSetup.ini, which contains metadata about the driver. I took interest in a property in the file: SilentInstallRun.” reads the report published by MrBrush. “When you double-click AsusSetup.exe it launches a simple gui installer thingy. But if you run AsusSetup.exe with the -s flag (DriverHub calls it using this to do a silent install), it will execute whatever’s specified in SilentInstallRun. In this case the ini file specifies a cmd script that performs an automated headless install of the driver, but it could run anything.”

The exploit chain abuses Asus DriverHub’s update mechanism: a malicious site on a spoofed subdomain sends requests to download a benign-sounding executable and a crafted AsusSetup.ini. Then, it downloads a legitimate, signed AsusSetup.exe, which runs silently with admin rights and executes the attacker’s payload (calc.exe) as specified in the .ini file.

MrBruh discovered the flaw on April 7 and reported the vulnerabilities on April 8. Asus released security updates on May 9.

MrBruh asked Asus if they offered bug bounties. The company said they don’t offer bug bounties but would add the researcher’s name to their “hall of fame.”

“I asked ASUS if they offered bug bounties. They responded saying they do not, but they would instead put my name in their “hall of fame”. This is understandable since ASUS is just a small startup and likely does not have the capital to pay a bounty.” concludes MrBruh.

Follow me on Twitter: @securityaffairs and Facebook and Mastodon

Pierluigi Paganini

(SecurityAffairs – hacking, ASUS)







Source link