OpenVPN / OpenVPN/openvpn

Random segfaults on OpenWrt 25.12.5

Open
#1,039 15 comments 0 reactions 2 assignees View on GitHub

@itsGiaan is already working on this.

Since May 19, 2026.

Dominant language
C
Stars
14.6k
Forks
3.4k
PR merge metrics
No merged PRs in 30d

Description

OS: OpenWRT 25.12.5
Hardware: AMD GX-412TC SOC
Version / Build: OpenVPN 2.7.4 x86_64-openwrt-linux-gnu [SSL (mbed TLS)] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] [DCO]
library versions: mbed TLS 3.6.6

segfault at 10 ip 00007fe131bac164 sp 00007ffc1cbd3ce8 error 4 in libc.so[45164,7fe131b7b000+58000] likely on CPU 3 (core 3, socket 0)
segfault at 10 ip 00007effc1da1164 sp 00007fff217a3958 error 4 in libc.so[45164,7effc1d70000+58000] likely on CPU 3 (core 3, socket 0)
segfault at 10 ip 00007eff41d04164 sp 00007ffdba7ed458 error 4 in libc.so[45164,7eff41cd3000+58000] likely on CPU 1 (core 1, socket 0)
segfault at 10 ip 00007f778ca97164 sp 00007ffe2e4a40d8 error 4 in libc.so[45164,7f778ca66000+58000] likely on CPU 1 (core 1, socket 0)
segfault at 10 ip 00007f662aaab164 sp 00007ffffb335808 error 4 in libc.so[45164,7f662aa7a000+58000] likely on CPU 3 (core 3, socket 0)
segfault at 10 ip 00007f5f2dcb1164 sp 00007fffaf7a35d8 error 4 in libc.so[45164,7f5f2dc80000+58000] likely on CPU 1 (core 1, socket 0)
segfault at 10 ip 00007fd9135b1164 sp 00007ffd070b2c08 error 4 in libc.so[45164,7fd913580000+58000] likely on CPU 0 (core 0, socket 0)
segfault at 10 ip 00007fc594402164 sp 00007ffed13f1958 error 4 in libc.so[45164,7fc5943d1000+58000] likely on CPU 2 (core 2, socket 0)
segfault at 10 ip 00007f9ab4a0e164 sp 00007fff895698a8 error 4 in libc.so[45164,7f9ab49dd000+58000] likely on CPU 1 (core 1, socket 0)
segfault at 10 ip 00007f622238e164 sp 00007ffde0745438 error 4 in libc.so[45164,7f622235d000+58000] likely on CPU 3 (core 3, socket 0)
segfault at 10 ip 00007fa2ffda2164 sp 00007fff9f699598 error 4 in libc.so[45164,7fa2ffd71000+58000] likely on CPU 0 (core 0, socket 0)
segfault at 10 ip 00007f62ada8a164 sp 00007fffc4e5f388 error 4 in libc.so[45164,7f62ada59000+58000] likely on CPU 2 (core 2, socket 0)
segfault at 10 ip 00007fa667c4f164 sp 00007fff7c3f37a8 error 4 in libc.so[45164,7fa667c1e000+58000] likely on CPU 3 (core 3, socket 0)
segfault at 10 ip 00007f2c4bbf0164 sp 00007fffdfcd7328 error 4 in libc.so[45164,7f2c4bbbf000+58000] likely on CPU 1 (core 1, socket 0)
segfault at 10 ip 00007f77ecea9164 sp 00007ffec80b54c8 error 4 in libc.so[45164,7f77ece78000+58000] likely on CPU 3 (core 3, socket 0)
segfault at 10 ip 00007f9b25aec164 sp 00007ffc3f853be8 error 4 in libc.so[45164,7f9b25abb000+58000] likely on CPU 3 (core 3, socket 0)
segfault at 10 ip 00007fedc9134164 sp 00007fff81e623a8 error 4 in libc.so[45164,7fedc9103000+58000] likely on CPU 2 (core 2, socket 0)
segfault at 10 ip 00007fdf8a608164 sp 00007ffd56e18838 error 4 in libc.so[45164,7fdf8a5d7000+58000] likely on CPU 2 (core 2, socket 0)
segfault at 10 ip 00007f49214f5164 sp 00007ffede30f2a8 error 4 in libc.so[45164,7f49214c4000+58000] likely on CPU 0 (core 0, socket 0)
segfault at 10 ip 00007f2741137164 sp 00007ffceebbde78 error 4 in libc.so[45164,7f2741106000+58000] likely on CPU 3 (core 3, socket 0)

Always at the same code:

Code: 1f 80 7f fc 00 74 11 85 f6 74 01 f4 8b 77 f8 81 fe ff ff 00 00 7f 01 f4 89 f0 c1 e0 04 48 98 48 29 c7 48 8b 47 f0 48 8d 4f f0 <48> 39 48 10 74 01 f4 0f b6 48 20 83 e1 1f 39 d1 7d 01 f4 8b 48 18

I have almost no information about why/what happened. But I control all the clients that can legitimately connect to this server, and none were running at that time. So it must have been caused by random attacks from the internet.
More may have occured earlier, but that syslog is gone. Some crashes came in packs of 1 to 4 during less than a minute, no noticeble pattern in rythm.

I find it worrying, that apparently random connections from the internet cause segfaults, hence this report.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.