Local user can trigger an assert in systemd, freezing PID 1
Key facts
- Attack vector
- Local
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-848h-497j-8vjq. Fix status from GitHub.
Summary
systemd is affected from version 260 before 260.1 and from 260 before 261. A flaw in the varlink IPC API lets a local unprivileged user make systemd running as PID 1 hit an assert and freeze execution. This is caused by a change introduced in v260, so earlier versions are not affected. The attacker needs only local access and no privileges, and the impact is availability loss (denial of service).
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Impact systemd (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data: ``` echo -ne '{"method": "io.systemd.UserDatabase.GetUserRecord", "parameters": {"fuzzyNames": [null,[]]}}\0' | socat - UNIX-CONNECT:/run/systemd/io.systemd.Manager ``` This is caused by a change in v260 (https://github.com/systemd/systemd/commit/799392286ec0797c0a2a1260c444360b47ef36fc), so earlier versions are not affected. ### Patches v261 https://github.com/systemd/systemd/commit/924f5a3461512ac8126fe4423329e3ca802b4d20 v260.1 https://github.com/systemd/systemd/commit/6f3074088a9f89f89d3188f7b3b4f0ddc0cfc73b ### Workarounds Change the access control of the varlink socket `/run/systemd/io.systemd.Manager` so that it is only accessible to root
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | systemd (linux) | 260 | 260.1 261 | Patch available | GHSA-848h-497j-8vjq |
- systemd (linux) Vendor— Affected 260 Fixed in 260.1 261 Patch available GHSA-848h-497j-8vjq
Remediation
Upgrade systemd to version 260.1 or 261. Commit 6f30740 fixes 260.1 and commit 924f5a3 fixes 261. As a workaround, restrict the access control of the varlink socket /run/systemd/io.systemd.Manager so that only root can access it.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-848h-497j-8vjq systemd (linux) Fixed in 260.1 261 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-848h-497j-8vjq
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences