systemd Vulnerabilities and Affected Products

systemd-machined: unprivileged users can terminate arbitrary processes

When systemd-machined >= v259 (or v258 with a custom `polkit` policy that allows `register-machine` access) is running on a desktop system, an unprivileged user logged in a desktop graphical session can kill arbitrary processes, even privileged ones. - versions older than v259 are not affected, unless unprivileged access is granted for the `register-machine` polkit action via a local, custom policy config file - versions older than v258 are not affected - unrelated to the systemd service manage…

systemd-homed: local privilege escalation via missing home-record signature verification on the authenticate path

systemd-homed contains a local privilege escalation bug via arbitrary system group addition to a local, logged in, homed-managed user

systemd-oomd: unprivileged users can terminate arbitrary processes

Local unprivileged users can terminate arbitrary local processes via a systemd-oomd IPC API due to a missing path traversal validation.

Generated title:systemd IPC API Null Element Assertion Denial of Service

In systemd 260 before 261, a local unprivileged user can trigger an assert via an IPC API call with an array or map that has a null element.

Generated title:systemd nspawn Escape-to-Host via Crafted Config File

In nspawn in systemd 233 through 259 before 260, an escape-to-host action can occur via a crafted optional config file.

Generated title:systemd udev Local Root Execution via Unsanitized Kernel Output

In udev in systemd before 260, local root execution can occur via malicious hardware devices and unsanitized kernel output.

Generated title:systemd systemd-machined Local Privilege Escalation via Varlink

In systemd 259 before 260, there is local privilege escalation in systemd-machined because varlink can be used to reach the root namespace.

Generated title:systemd Assertion Failure via Delegate=yes Unit with Unset User

In systemd 258 before 260, a local unprivileged user can trigger an assert when a Delegate=yes and User=<unset> unit exists and is running.

systemd: Local unprivileged user can trigger an assert

systemd, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this is not possible as the safety check causes an assert instead. This IPC call was added in v239, so versions older than that are not affected. Versions 260-rc1, 259.2, 258.5, and 257.11 contain patches. N…

systemd 37-1 does not properly handle non-existent services, which causes a denial of service (failure of login procedure).