CVE-2022-45873 — systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a...
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+3
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
- Documented patch — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Fedoraproject Fedora, Systemd Project Systemd).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Fedoraproject | Fedora | version 36 | Vulnerable | NIST National Vulnerability Database |
| Systemd Project | Systemd | ≥ 250 and ≤ 251version 252-rc1version 252-rc2 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 5.5 | CVSS 3.1 | Medium | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Track CPU/memory spikes and availability drops correlated with request patterns.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · systemd project/systemd, fedoraproject/fedora
- CVSS changed · 5.5
- Source status changed · → Modified
- Record created in this database
- 2022
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
9 on the record
- github.com/systemd/systemd/pull/25055
- github.com/systemd/systemd/pull/24853
- github.com/systemd/systemd/commit/076b807be472630692c5348c60d0c2b7b28ad437
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MS5N
- cert-portal.siemens.com/productcert/html/ssa-398330.html
- github.com/advisories/GHSA-3w8w-mhj7-j5rc
- nvd.nist.gov/vuln/detail/CVE-2022-45873
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MS5N
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MS5N5S
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-54231 Abrt: unsanitized systemd journal content written to dump directory files enables content injection Jun 13, 2026
- High CVE-2026-54230 Abrt: event handler scripts follow symlinks when writing output files, allowing arbitrary file overwrites Jun 13, 2026
- Medium CVE-2026-40225 Incorrect Resource Transfer Between Spheres in Systemd Project Systemd Apr 10, 2026
- High CVE-2026-40224 Incorrect Authorization in Systemd Project Systemd Apr 10, 2026
- Medium CVE-2026-40226 In nspawn in systemd 233 through 259 before 260, an escape-to-host action can occur via… Apr 10, 2026
- Low CVE-2026-40228 Incorrect Resource Transfer Between Spheres in Systemd Project Systemd Apr 10, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2022-45873 is "systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a...", rated Medium. It affects Fedora (Fedoraproject); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.27% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.