Skip to content
Noroxi
CVE-2022-45873· NVD / CVE Program· CNA mitre

systemd 250 and 251 allows local users to achieve a systemd-coredump deadlock by triggering a crash that has a long backtrace.

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
  • 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.
  • Fixed version: systemd (AlmaLinux:9) 250-12.el9_1.3; systemd-container (AlmaLinux:9) 250-12.el9_1.3; systemd-devel (AlmaLinux:9) 250-12.el9_1.3.

Low priority for now. Upgrade to systemd (AlmaLinux:9) 250-12.el9_1.3; systemd-container (AlmaLinux:9) 250-12.el9_1.3; systemd-devel (AlmaLinux:9) 250-12.el9_1.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Nov 23, 2022
Updated
Jun 17, 2026
EPSS
0.3% · 17th percentile

Report tools

JSON

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.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-45873

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for systemd project records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
systemd projectsystemd
fedoraprojectfedora

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.

EcosystemPackageAffected rangeFix
AlmaLinux:9systemdbefore 250-12.el9_1.3250-12.el9_1.3
AlmaLinux:9systemd-containerbefore 250-12.el9_1.3250-12.el9_1.3
AlmaLinux:9systemd-develbefore 250-12.el9_1.3250-12.el9_1.3
AlmaLinux:9systemd-journal-remotebefore 250-12.el9_1.3250-12.el9_1.3
AlmaLinux:9systemd-libsbefore 250-12.el9_1.3250-12.el9_1.3
AlmaLinux:9systemd-oomdbefore 250-12.el9_1.3250-12.el9_1.3
AlmaLinux:9systemd-pambefore 250-12.el9_1.3250-12.el9_1.3
AlmaLinux:9systemd-resolvedbefore 250-12.el9_1.3250-12.el9_1.3
AlmaLinux:9systemd-rpm-macrosbefore 250-12.el9_1.3250-12.el9_1.3
AlmaLinux:9systemd-udevbefore 250-12.el9_1.3250-12.el9_1.3
Debian:12systemdbefore 252-1252-1
Red Hat:enterprise_linux:9::appstreamsystemd-container-debuginfobefore 0:250-12.el9_1.30:250-12.el9_1.3
Red Hat:enterprise_linux:9::appstreamsystemd-debuginfobefore 0:250-12.el9_1.30:250-12.el9_1.3
Red Hat:enterprise_linux:9::appstreamsystemd-debugsourcebefore 0:250-12.el9_1.30:250-12.el9_1.3
Red Hat:enterprise_linux:9::appstreamsystemd-develbefore 0:250-12.el9_1.30:250-12.el9_1.3
Red Hat:enterprise_linux:9::appstreamsystemd-devel-debuginfobefore 0:250-12.el9_1.30:250-12.el9_1.3
Red Hat:enterprise_linux:9::appstreamsystemd-journal-remotebefore 0:250-12.el9_1.30:250-12.el9_1.3
Red Hat:enterprise_linux:9::appstreamsystemd-journal-remote-debuginfobefore 0:250-12.el9_1.30:250-12.el9_1.3
Red Hat:enterprise_linux:9::appstreamsystemd-libs-debuginfobefore 0:250-12.el9_1.30:250-12.el9_1.3
Red Hat:enterprise_linux:9::appstreamsystemd-oomd-debuginfobefore 0:250-12.el9_1.30:250-12.el9_1.3
Red Hat:enterprise_linux:9::appstreamsystemd-pam-debuginfobefore 0:250-12.el9_1.30:250-12.el9_1.3
Red Hat:enterprise_linux:9::appstreamsystemd-resolved-debuginfobefore 0:250-12.el9_1.30:250-12.el9_1.3
Red Hat:enterprise_linux:9::appstreamsystemd-standalone-sysusers-debuginfobefore 0:250-12.el9_1.30:250-12.el9_1.3
Red Hat:enterprise_linux:9::appstreamsystemd-standalone-tmpfiles-debuginfobefore 0:250-12.el9_1.30:250-12.el9_1.3

+10

Same product

systemd project: all records

Other 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 th
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:systemd250-12.el9_1.3 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-container250-12.el9_1.3 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-devel250-12.el9_1.3 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-journal-remote250-12.el9_1.3 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-libs250-12.el9_1.3 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-oomd250-12.el9_1.3 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-pam250-12.el9_1.3 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-resolved250-12.el9_1.3 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-rpm-macros250-12.el9_1.3 · AlmaLinux:9Package registry (OSV)
almalinux:systemd-udev250-12.el9_1.3 · AlmaLinux:9Package registry (OSV)
debian:systemd252-1 · Debian:12Package registry (OSV)
red hat:systemd-container-debuginfo0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:systemd-debuginfo0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:systemd-debugsource0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:systemd-devel0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:systemd-devel-debuginfo0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:systemd-journal-remote0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:systemd-journal-remote-debuginfo0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:systemd-libs-debuginfo0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:systemd-oomd-debuginfo0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:systemd-pam-debuginfo0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:systemd-resolved-debuginfo0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:systemd-standalone-sysusers-debuginfo0:250-12.el9_1.3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:systemd0:250-12.el9_1.3 · Rocky Linux:9Package 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.

EPSS, last 120 days

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 researchers

Finders, 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 Consumption

CVSS 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 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
function expand(node) {  return node.children.map(expand);}

Fixed

ts
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.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records