SUSE · Security update for systemd
Affects SUSESource GCVE Database
Not known to be exploited · CVSS 4.7 Medium · fixed in Red Hat Enterprise Linux 10 package updates : update SUSE systemd-coredump when convenient.
Data as of 15 Nov 2026, 22:50 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 4.7 |
|---|
- Patch
- Available – fixed in 257.6, 256.14, 255.19 +3
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| systemd-coredump | Affected
| Fixed in
|
| systemd-coredump | Affected
| Fixed in
|
| systemd-coredump | Affected
| Fixed in
|
| systemd-coredump | Affected
| Fixed in
|
| systemd-coredump | Affected
| Fixed in
|
| systemd-coredump | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
This update for systemd fixes the following issues: - coredump: use %d in kernel core pattern (CVE-2025-4598) - Revert "macro: terminate the temporary VA_ARGS_FOREACH() array with a sentinel" (SUSE specific) - umount: do not move busy network mounts (bsc#1236177) - man/pstore.conf: pstore.conf template is not always installed in /etc - man: coredump.conf template is not always installed in /etc (bsc#1237496) - Don't write messages sent from users with UID falling into the container UID range to the system journal. Daemons in the container don't talk to the outside journald as they talk to the inner one directly, which does its journal splitting based on shifted uids. (bsc#1242938) - This re-adds back the support for the persistent net name rules as well as their generator since predictable naming scheme is still disabled by default on Micro (via the `net.ifnames=0` boot option). (bsc#1241190)
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/2025/suse-su-2025_20405-1.json (opens in a new tab)
- suse.com/support/update/announcement/2025/suse-su-202520405-1/ (opens in a new tab)
- lists.suse.com/pipermail/sle-updates/2025-June/040342.html (opens in a new tab)
- bugzilla.suse.com/1236177 (opens in a new tab)
- bugzilla.suse.com/1237496 (opens in a new tab)
- bugzilla.suse.com/1241190 (opens in a new tab)
- bugzilla.suse.com/1242938 (opens in a new tab)
- suse.com/security/cve/CVE-2025-4598/ (opens in a new tab)