Public bug reported:
We have a physical server running Ubuntu 20.04.6 LTS (amd64) and openssh-server
1:8.2p1-4ubuntu0.9. Sometimes sshd crashes with a segmentation fault on remote
login with key authentication:
[193107.651745] sshd[1229630]: segfault at 5557eba6a008 ip 7f2326a2ca53 sp
7
Thanks for getting back to me!
1. The crash seems to happen in a large percentage of the runs of a particular
test that does a lot of rapid SSH connections to the machine. Sadly, I don’t
have an exact number, but 50% probably wouldn’t be an exaggeration. It was also
happening in the setup part
While trying to reproduce the segfault, I encountered another crash, an
abort in malloc this time. I cannot be absolutely sure, but it seems
that they might be related, so I am uploading the report now.
Edit: forgot to mention, it seems that the abort has also occurred on
the physical machine that
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2043114/+attachment/5717894/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2043114/+attachment/5717893/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bug
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2043114/+attachment/5717895/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.
Apologies for the multiple messages, but I was under the impression that
apport-collect would upload the actual core dump file here :)
** Attachment added: "sshd abort crash report"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2043114/+attachment/5717896/+files/_usr_sbin_sshd.0.crash
After some more "stress testing" with GNU parallel, I was able to
reproduce the segmentation fault, too. See attachment.
** Attachment added: "sshd segmentation fault crash report"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2043114/+attachment/5717935/+files/_usr_sbin_sshd.0.crash
Yes, seems pretty consistent. I just tried it again before I write out
the reproduction steps, and it took maybe a couple of minutes.
The configuration is basically just:
sed -i.bak 's/#LogLevel INFO/LogLevel DEBUG/g' /etc/ssh/sshd_config
systemctl restart sshd
As for making enough connections t
We’re seeing it happen on both bare metal and virtual machines.
The VMs are libvirt/QEMU/KVM managed by OpenNebula. The hypervisor is
running AlmaLinux 8 with the 4.18.0-477.15.1.el8_8.x86_64 kernel. The
VMs have 2 physical/8 vCPUs allocated to them. The VM I used for the
reproduction has 2GB of R
10 matches
Mail list logo
