# SUSE-SU-2026:3122-1: Security update for systemd, systemd-mini

> An attacker with local access can cause a denial of service in systemd by providing invalid characters in SCSI ID fields.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jul 2026

## What is SUSE-SU-2026:3122-1?

SUSE-SU-2026:3122-1 is a vulnerability in systemd, published on 20 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This update for systemd, systemd-mini fixes the following issues

Changes for systemd:

- Import commit 435c5779a785b4263b4dcacb70f50ef1cc3f9a7b (bsc#1267647).
- Import commit 7aa089f75b77b2db22941081c37b8917ea8d0dda (bsc#1261982).
- udev/scsi-id: check for invalid chars in various fields received from the kernel.

## Which versions are affected by SUSE-SU-2026:3122-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `systemd` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 228-157.82.1 |

## How do I fix SUSE-SU-2026:3122-1?

Apply the vendor's patch.

## Is SUSE-SU-2026:3122-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2026:3122-1 is a vulnerability in systemd, published on 20 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2026:3122-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/SUSE-SU-2026-3122-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-3122-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2026:3122-1

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