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

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.

   Simon

-- System Information:
Debian Release: 13.4
  APT prefers stable-security
  APT policy: (990, 'stable-security'), (990, 'stable'), (500, 'stable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.74+deb13+1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages libc6 depends on:
ii  libgcc-s1  14.2.0-19

Versions of packages libc6 recommends:
ii  libidn2-0  2.3.8-2

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.91
pn  glibc-doc              <none>
ii  libc-l10n              2.41-12+deb13u2
pn  libnss-nis             <none>
pn  libnss-nisplus         <none>
ii  locales                2.41-12+deb13u2

-- debconf information excluded