# openSUSE-SU-2026:21222-1: Security update for systemd

> Security update for systemd addressing TLS allocation failures and debugfs mounting defaults, requiring patching on openSUSE systems.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 3 Jul 2026

## What is openSUSE-SU-2026:21222-1?

openSUSE-SU-2026:21222-1 is a vulnerability in systemd, published on 3 Jul 2026. 

### Official description

This update for systemd fixes the following issues:

Changes in systemd:

- Better handle TLS allocation failure (bsc#1254924).
- Disable mounting `debugfs` by default (jsc#PED-8812).
- Import commit 9e8b5afe0fb2061f4a17a3022469dd62f2683960 (bsc#1267647 bsc#1267644 bsc#1262305 bsc#1263117).
- Move `systemd-pcrlock` out from the experimental sub-package to `udev` (bsc#1248261 jsc#PED-15946).
- Add a weak runtime dependency on `libtss2-tcti-device0` (bsc#1260357).
- Import commit 59336000ef7850eba0963c6a690ff3371c425929 (bsc#1261982 bsc#1261983).
- Add a weak runtime dependency on `polkit` (bsc#1259071).
- systemd-update-helper: fix the clean-state command only removing `$STATE_DIR/system` instead of `$STATE_DIR/`.
- systemd-update-helper: add `--root` option for testing convenience.
- systemd-update-helper: fix incorrect skipping of `systemctl disable` during package removal (bsc#1245551).
- systemd-update-helper: fix `do_install_units()` incorrectly returning 1 when no units need preset.
- systemd.spec: introduce `%bcond_without` docs to allow skipping man pages and `devel-doc`.
- systemd.spec: drop the `%{release}` number from the SBAT version (bsc#1251948).

## Which versions are affected by openSUSE-SU-2026:21222-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `systemd` | openSUSE:Leap 16.0 | All versions | 257.13-160000.2.1 |
| `systemd-mini` | openSUSE:Leap 16.0 | All versions | 257.13-160000.2.1 |

## How do I fix openSUSE-SU-2026:21222-1?

Apply the vendor's patch.

## Is openSUSE-SU-2026:21222-1 being exploited?

There is no known exploitation of openSUSE-SU-2026:21222-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for openSUSE-SU-2026:21222-1 and fix it if it is affected.

What it is: openSUSE-SU-2026:21222-1 is a vulnerability in systemd, published on 3 Jul 2026. 
Exploitation: There is no known exploitation of openSUSE-SU-2026:21222-1 in the wild and no public exploit code.

Affected product: systemd. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/openSUSE-SU-2026-21222-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2026-21222-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2026:21222-1

---
From sbomify Insights: https://insights.sbomify.com/openSUSE-SU-2026-21222-1/
Summaries are generated and may contain mistakes; the official description above is the record.