Bug 2149063 (CVE-2022-45873) - CVE-2022-45873 systemd: deadlock in systemd-coredump via a crash with a long backtrace
Summary: CVE-2022-45873 systemd: deadlock in systemd-coredump via a crash with a long ...
Status: NEW
Alias: CVE-2022-45873
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 2149074 2149075 2149066 2149072 2149073 2149100
Blocks: 2147551
TreeView+ depends on / blocked
Reported: 2022-11-28 17:53 UTC by Guilherme de Almeida Suckevicz
Modified: 2022-12-12 17:47 UTC (History)
46 users (show)

Fixed In Version: systemd 252-rc3
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the systemd-coredump utility of systemd. When an application crashes, the systemd-coredump utility is called twice, once by the kernel and the second time in the systemd-coredump@.service to write the data, process, and save the core file. Communication between the programs is made through a pipe, and when there is too much data through a long backtrace or many linked libraries, the pipe blocks while waiting for the data, resulting in a timeout of the systemd-coredump@.service.
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2022-11-28 17:53:46 UTC
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.


Upstream patch:

Comment 1 Guilherme de Almeida Suckevicz 2022-11-28 18:06:51 UTC
Created systemd tracking bugs for this issue:

Affects: fedora-all [bug 2149066]

Note You need to log in before you can comment on or make changes to this bug.