Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#62505 - [systemd] bug in internal memory management leads to crashes

Attached to Project: Arch Linux
Opened by Aaron Barany (akb825) - Monday, 29 April 2019, 22:40 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 14 May 2019, 18:38 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


systemd has a critical bug related to its internal memory management that can cause crashes. When re-allocating internal arrays, some parts at the end won't be copied, causing some parts of the array to become uninitialized.

In my situation, bringing up a file load dialog called into a libsystemd function to enumerate the devices. When the device list was built up, re-allocation of the device array caused some elements to be uninitialized, crashing the program.

Additional info:
* package version: 242
* github bug:
* commit that introduced the bug:
* github pull request to revert the commit:

Steps to reproduce:
This happened to me in a Qt application when default constructing a QFileDialog on a KDE system, which happened to call the libsystemd function when enumerating the devices. Reproduction of this issue will be highly dependent on:
1. The situations that call libsystemd functions that themselves call the reallocation function.
2. Cases where a reallocation will be required. For example, when enumerating the devices, the bug will only happen once you have enough devices that it needs to re-allocate the array. (in this case it re-allocated on the 9th device)
This task depends upon

Closed by  Antonio Rojas (arojas)
Tuesday, 14 May 2019, 18:38 GMT
Reason for closing:  Fixed
Comment by Andrej Podzimek (andrej) - Thursday, 09 May 2019, 01:58 GMT
Could this be related?
Or maybe also this?
This has just given me a tremendously hard time on my server. :-(
Comment by Aaron Barany (akb825) - Friday, 10 May 2019, 18:35 GMT
The patch is now applied on the v242 stable branch.
Comment by loqs (loqs) - Friday, 10 May 2019, 21:59 GMT
Can you confirm the issue has been fixed in systemd 242.29-1 currently in testing?
Comment by Aaron Barany (akb825) - Saturday, 11 May 2019, 08:36 GMT
I won't be able to confirm until Monday unfortunately, but so long as it contains the latest commits added earlier today it should fix the issue.
Comment by Aaron Barany (akb825) - Monday, 13 May 2019, 21:48 GMT
I can confirm that the latest version fixes the issue.