Version-Release number of selected component: systemd-239-12.git8bca462.fc29 Additional info: reporter: libreport-2.10.0 backtrace_rating: 3 cmdline: /usr/lib/systemd/systemd --user executable: /usr/lib/systemd/systemd journald_cursor: s=1de52392a41c448f91f92b688a823a97;i=13c77;b=99a7244c55484f9d9f046ad2f0ddbe52;m=3d3cd5d36;t=5854eab924e66;x=d055130f6a237de2 kernel: 5.0.4-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ?? #1 deinit at cap-ng.c:161 #2 __run_fork_handlers at register-atfork.c:134 #3 __libc_fork at ../sysdeps/nptl/fork.c:137 #4 exec_spawn at ../src/core/execute.c:3497 #5 service_spawn at ../src/core/service.c:1463 #6 service_enter_start at ../src/core/service.c:1961 #7 service_enter_start_pre at ../src/core/service.c:2029 #8 service_start at ../src/core/service.c:2272 #9 unit_start at ../src/core/unit.c:1850
Created attachment 1549779 [details] File: backtrace
Created attachment 1549780 [details] File: cgroup
Created attachment 1549781 [details] File: core_backtrace
Created attachment 1549782 [details] File: cpuinfo
Created attachment 1549783 [details] File: dso_list
Created attachment 1549784 [details] File: environ
Created attachment 1549785 [details] File: limits
Created attachment 1549786 [details] File: maps
Created attachment 1549787 [details] File: mountinfo
Created attachment 1549788 [details] File: open_fds
Created attachment 1549789 [details] File: proc_pid_status
Created attachment 1549790 [details] File: var_log_messages
Created attachment 1549791 [details] File: exploitable
I think this might be related to this patch: https://github.com/stevegrubb/libcap-ng/commit/7759e6f8469eb33aef1a1d5eba5d300c3a8fcb63 Steve, any idea why it would crashing here?
This was found by bug 1680481. That has some more background information. This was subsequently fixed in libcap-ng-0.7.9-7. This appears to be reported about the time that it was found in apache. I'd say this bug report can be closed since the fix was pushed out a long time ago.
Many thanks! *** This bug has been marked as a duplicate of bug 1680481 ***