systemd vulnerabilities

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 manager (pid 1 or user session managers) - systemd-machined is not typically installed by default, and is typically in an optional, separate package (e.g.:

• Update to 259.5-0ubuntu3.4

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

• Update to 259.5-0ubuntu3.4

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.

• Update to 259.5-0ubuntu3.4

CVE-2026-40228

In systemd 259, systemd-journald can send ANSI escape sequences to the terminals of arbitrary users when a "logger -p emerg" command is executed, if ForwardToWall=yes is set.