1.9.8 fails to start: *** buffer overflow detected ***: terminated

Bug #1894809 reported by Iain Lane
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
haveged (Ubuntu)
Fix Released
Undecided
Unassigned
Groovy
Fix Released
Undecided
Unassigned

Bug Description

1.9.8 fails to start like this:

(gdb) run
Starting program: /usr/sbin/haveged --Foreground --verbose=1
haveged: can not bind a name to UNIX socket
haveged: can not initialize command socket: Permission denied
haveged starting up
haveged: ver: 1.9.8; arch: x86; vend: GenuineIntel; build: (gcc 10.2.0 ITV); collect: 128K
haveged: cpu: (L4 VC); data: 32K (L2 L4 V); inst: 32K (L2 L4 V); idx: 24/40; sz: 32154/54079
haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B): last entropy estimate 8.00001
haveged: fills: 0, generated: 0
*** buffer overflow detected ***: terminated

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007f02ed903859 in __GI_abort () at abort.c:79
#2 0x00007f02ed96e44e in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f02eda9807c "*** %s ***: terminated\n")
    at ../sysdeps/posix/libc_fatal.c:155
#3 0x00007f02eda10c3a in __GI___fortify_fail (msg=msg@entry=0x7f02eda98012 "buffer overflow detected") at fortify_fail.c:26
#4 0x00007f02eda0f4d6 in __GI___chk_fail () at chk_fail.c:28
#5 0x00007f02eda10b7b in __fdelt_chk (d=<optimized out>) at fdelt_chk.c:25
#6 0x000055881936f454 in run_daemon (argv=0x7ffcceac7428, path=0x55881ac7a2a0 "/usr/sbin/haveged", h=0x55881ac7a8b0) at haveged.c:584
#7 main (argc=<optimized out>, argv=<optimized out>) at haveged.c:470

Revision history for this message
Iain Lane (laney) wrote :

We detected this in systemd's autopkgtest, which checks there are no failed units.

Ideally haveged would have caught this itself. The 'make check' autopkgtest, though, builds haveged fresh and then checks the thing it just built. It doesn't check the binaries that are in the archive, and neither does it check the systemd unit. That should be improved, I think.

summary: - 1.9.8 fails to start
+ 1.9.8 fails to start: *** buffer overflow detected ***: terminated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in haveged (Ubuntu):
status: New → Confirmed
Dan Streetman (ddstreet)
tags: removed: block-proposed-groovy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package haveged - 1.9.8-4ubuntu3

---------------
haveged (1.9.8-4ubuntu3) groovy; urgency=medium

  * d/p/lp1894865-Fixed-https-github.com-jirka-h-haveged-issues-29.patch:
    - Fix segfault when using --Foreground param (LP: #1894809)
  * d/p/lp1894877-don-t-fail-completely-if-we-can-t-set-write-wakeup-w.patch:
    - Don't fail if -w is used in a container (LP: #1894877)
  * d/haveged.default:
    - remove -w param by default
  * d/apparmor-profile:
    - allow haveged to actually output to stdout/stderr (LP: #1894905)
    - allow haveged to bind to unix sockets
  * d/haveged.service:
    - add ConditionVirtualization=!container
  * d/t/control, d/t/dieharder, d/t/run-tests, d/t/check-service:
    - restore dieharder test, but with limited tests
    - verify haveged service is active
    - fix run-tests to check installed haveged
    - skip dieharder tests on s390x, where dieharder is broken

 -- Dan Streetman <email address hidden> Fri, 11 Sep 2020 13:40:44 -0400

Changed in haveged (Ubuntu Groovy):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.