Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

When trying to use clevis to unlock multiple LUKS devices automatically, systemd-cryptsetup crashes with SIGABRT.


Version-Release number of selected component (if applicable):

systemd-239-13.el8.x86_64

How reproducible:
Always, when using a clevis setup as per https://bugzilla.redhat.com/show_bug.cgi?id=1751912


Steps to Reproduce:
1.  Install RHEL 8.0 w/ multiple LUKS1 devices
2.  Configure the LUKS devices to be decrypted with tang server
3.  Reboot

Actual results:

systemd-cryptsetup will crash due to memory corruption.
journalctl will have messages like the following:

systemd-cryptsetup@luks\x2dc695d0af\x2db6a0\x2d4e93\x2d941f\x2d53c0f36c865d.service: Main process exited, code=dumped, status=6/ABRT
Sep 13 07:11:47 rhel-luks1 systemd[1]: systemd-cryptsetup@luks\x2dc695d0af\x2db6a0\x2d4e93\x2d941f\x2d53c0f36c865d.service: Failed with result 'core-dump'.
Sep 13 07:11:47 rhel-luks1 systemd[1]: Failed to start Cryptography Setup for luks-c695d0af-b6a0-4e93-941f-53c0f36c865d.


Expected results:

No crashes in systemd-cryptsetup.

Additional info:

Backporting this upstream fix resolves this particular memory corruption: https://github.com/systemd/systemd/commit/59c55e73eaee345e1ee67c23eace8895ed499693

PR: https://github.com/systemd-rhel/rhel-8/pull/20

*** Bug 1759954 has been marked as a duplicate of this bug. ***

fix merged to github master branch -> https://github.com/systemd-rhel/rhel-8/pull/20 -> post

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1794