CVE-2022-45873: systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a

Q: How do I fix CVE-2022-45873?

systemd: upgrade to newer than 251; fedora: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2022-45873 being exploited?

CVE-2022-45873 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-45873 affect?

CVE-2022-45873 affects systemd, fedora. Severity is medium (CVSS 5.5). 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 t

Q: How urgent is CVE-2022-45873?

Priority 24/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADEMITIGATE

CVE-2022-45873 is a medium-severity flaw (CVSS 5.5) affecting systemd, fedora. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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/sys

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 81%)
CISA exploited list	No
Weakness	CWE-400
Published	2022-11-23
Last modified	2026-10-14

Publisher (CNA): MITRE · Vendor: fedoraproject · systemd project

Last updated 2026-10-14 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-11-23 23:15 UTCPublished CVE record published
2026-10-14 19:16 UTCUpdated Record last modified

systemd project systemd UPGRADE

Affected: >= 250 and <= 251 · 252 rc1 · 252 rc2

Fixed in: newer than 251

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy systemd || rpm -q systemd || systemd --version

2. UPGRADE to newer than 251 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade systemd

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade systemd

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

fedoraproject fedora MITIGATE

Affected: 36

Fixed in: no fixed release known

Safe to downgrade to: a release before 36

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-45873?

systemd: upgrade to newer than 251; fedora: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-45873 being exploited?

CVE-2022-45873 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-45873 affect?

CVE-2022-45873 affects systemd, fedora. Severity is medium (CVSS 5.5). 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 t

How urgent is CVE-2022-45873?

Priority 24/100. No elevated risk signals yet.

Related CVEs

CVE-2023-7008 MEDIUM 5.9 MITIGATE A vulnerability was found in systemd-resolved
CVE-2021-3997 MEDIUM 5.5 UPGRADE MITIGATE A flaw was found in systemd
CVE-2023-26604 HIGH 7.8 MITIGATE UPGRADE systemd before 247 does not adequately block local privilege escalation for some Sudo configurations, e.g., pl
CVE-2022-3821 MEDIUM 5.5 UPGRADE MITIGATE An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c
CVE-2021-33910 MEDIUM 5.5 UPGRADE MITIGATE basic/unit-name.c in systemd prior to 246.15, 247.8, 248.5, and 249.1 has a Memory Allocation with an Excessiv

References

← Back to latest CVEs