Bug#1134384: _exit uses NR_exit_group, leading to SIGKILL in seccomp

Aurelien Jarno <[email protected]> Sun, 19 Apr 2026 13:53:29 +0200
Newsgroups gmane.linux.debian.devel.glibc
Message-ID <aeTCOVd36VDQ-RWC__40142.9611070611$1776599726$gmane$org@aurel32.net>
Hi,

On 2026-04-19 20:31, Simon Richter wrote:
> Package: libc6
> Version: 2.41-12+deb13u2
> Severity: minor
> Tags: upstream
> X-Debbugs-Cc: [email protected]
> 
> Hi,
> 
> I have an application that uses seccomp in strict mode. When the
> application is finished, it uses the _exit(2) system call to terminate, as
> documented in seccomp(2). glibc however uses NR_exit_group, which is a
> seccomp violation, so the process is ended with SIGKILL instead.

Yes, glibc does that since version 2.3 in order to terminate all 
threads. I fail to see why it's a glibc issue though, this looks like 
more a seccomp decision to not allow this syscall in strict mode.

Regards
Aurelien