systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a long backtrace.
systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a long backtrace. This occurs in parse_elf_object in shared/elf-util.c. The exploitation methodology is to crash a binary calling the same function recursively, and put it in a deeply nested directory to make its backtrace large enough to cause the deadlock. This must be done 16 times when MaxConnections=16 is set for the systemd/units/systemd-coredump.socket file.
- Published
- Nov 23, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 17th percentile
- CWE
- CWE-400
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| systemd project | systemd | cpe:2.3:a:systemd_project:systemd |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora36
- systemd project systemd250 and later · up to 251 inclusive
- systemd project systemd252
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | systemd | before 250-12.el9_1.3 | 250-12.el9_1.3 |
| AlmaLinux:9 | systemd-container | before 250-12.el9_1.3 | 250-12.el9_1.3 |
| AlmaLinux:9 | systemd-devel | before 250-12.el9_1.3 | 250-12.el9_1.3 |
| AlmaLinux:9 | systemd-journal-remote | before 250-12.el9_1.3 | 250-12.el9_1.3 |
| AlmaLinux:9 | systemd-libs | before 250-12.el9_1.3 | 250-12.el9_1.3 |
| AlmaLinux:9 | systemd-oomd | before 250-12.el9_1.3 | 250-12.el9_1.3 |
| AlmaLinux:9 | systemd-pam | before 250-12.el9_1.3 | 250-12.el9_1.3 |
| AlmaLinux:9 | systemd-resolved | before 250-12.el9_1.3 | 250-12.el9_1.3 |
| AlmaLinux:9 | systemd-rpm-macros | before 250-12.el9_1.3 | 250-12.el9_1.3 |
| AlmaLinux:9 | systemd-udev | before 250-12.el9_1.3 | 250-12.el9_1.3 |
| Debian:12 | systemd | before 252-1 | 252-1 |
| Red Hat:enterprise_linux:9::appstream | systemd-container-debuginfo | before 0:250-12.el9_1.3 | 0:250-12.el9_1.3 |
| Red Hat:enterprise_linux:9::appstream | systemd-debuginfo | before 0:250-12.el9_1.3 | 0:250-12.el9_1.3 |
| Red Hat:enterprise_linux:9::appstream | systemd-debugsource | before 0:250-12.el9_1.3 | 0:250-12.el9_1.3 |
| Red Hat:enterprise_linux:9::appstream | systemd-devel | before 0:250-12.el9_1.3 | 0:250-12.el9_1.3 |
| Red Hat:enterprise_linux:9::appstream | systemd-devel-debuginfo | before 0:250-12.el9_1.3 | 0:250-12.el9_1.3 |
| Red Hat:enterprise_linux:9::appstream | systemd-journal-remote | before 0:250-12.el9_1.3 | 0:250-12.el9_1.3 |
| Red Hat:enterprise_linux:9::appstream | systemd-journal-remote-debuginfo | before 0:250-12.el9_1.3 | 0:250-12.el9_1.3 |
| Red Hat:enterprise_linux:9::appstream | systemd-libs-debuginfo | before 0:250-12.el9_1.3 | 0:250-12.el9_1.3 |
| Red Hat:enterprise_linux:9::appstream | systemd-oomd-debuginfo | before 0:250-12.el9_1.3 | 0:250-12.el9_1.3 |
| Red Hat:enterprise_linux:9::appstream | systemd-pam-debuginfo | before 0:250-12.el9_1.3 | 0:250-12.el9_1.3 |
| Red Hat:enterprise_linux:9::appstream | systemd-resolved-debuginfo | before 0:250-12.el9_1.3 | 0:250-12.el9_1.3 |
| Red Hat:enterprise_linux:9::appstream | systemd-standalone-sysusers-debuginfo | before 0:250-12.el9_1.3 | 0:250-12.el9_1.3 |
| Red Hat:enterprise_linux:9::appstream | systemd-standalone-tmpfiles-debuginfo | before 0:250-12.el9_1.3 | 0:250-12.el9_1.3 |
+10
Same product
systemd project: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-9445In systemd through 233, certain sizes passed to dns_packet_new in systemd-resolved can cause it to allocate a buffer that's too small.46Plan
- CVE-2018-21029systemd 239 through 245 accepts any certificate signed by a trusted certificate authority for DNS Over TLS.40Plan
- CVE-2015-7510Stack-based buffer overflow in the getpwnam and getgrnam functions of the NSS module nss-mymachines in systemd.40Plan
- CVE-2017-1000082systemd v233 and earlier fails to safely parse usernames starting with a numeric digit (e.g.40Plan
- CVE-2022-2526A use-after-free vulnerability was found in systemd.39Monitor
- CVE-2017-15908In systemd 223 through 235, a remote DNS server can respond with a custom crafted DNS NSEC resource record to trigger an infinite loop in th37Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:systemd | 250-12.el9_1.3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:systemd-container | 250-12.el9_1.3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:systemd-devel | 250-12.el9_1.3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:systemd-journal-remote | 250-12.el9_1.3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:systemd-libs | 250-12.el9_1.3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:systemd-oomd | 250-12.el9_1.3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:systemd-pam | 250-12.el9_1.3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:systemd-resolved | 250-12.el9_1.3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:systemd-rpm-macros | 250-12.el9_1.3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:systemd-udev | 250-12.el9_1.3 · AlmaLinux:9 | Package registry (OSV) |
| debian:systemd | 252-1 · Debian:12 | Package registry (OSV) |
| red hat:systemd-container-debuginfo | 0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:systemd-debuginfo | 0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:systemd-debugsource | 0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:systemd-devel | 0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:systemd-devel-debuginfo | 0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:systemd-journal-remote | 0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:systemd-journal-remote-debuginfo | 0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:systemd-libs-debuginfo | 0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:systemd-oomd-debuginfo | 0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:systemd-pam-debuginfo | 0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:systemd-resolved-debuginfo | 0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:systemd-standalone-sysusers-debuginfo | 0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:systemd | 0:250-12.el9_1.3 · Rocky Linux:9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- github.com/systemd/systemd/commit/076b807be472630692c5348c60d0c2b7b28ad437
- github.com/systemd/systemd/pull/24853#issuecomment-1326561497
- github.com/systemd/systemd/pull/25055#issuecomment-1313733553
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MS5N5SLYAHKENLAJWYBDKU55ICU3SVZF/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.