Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-152948

catatonit-0.2.1-3.el10.x86_64 segfaults immediately on startup

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • rhel-10.3
    • CentOS Stream 10
    • catatonit
    • None
    • catatonit-0.2.1-4.el10
    • None
    • Critical
    • rhel-container-tools
    • 1
    • 3
    • None
    • RUN 285
    • x86_64
    • None

      What were you trying to do that didn't work?

      Start Podman pods. The pod infra container uses catatonit as its init process, and catatonit segfaults immediately on startup before reaching main().

      What is the impact of this issue to you?

      All Podman pods fail to start. Pod containers fail with open /proc/<PID>/ns/net: No such file or directory because the infra container (catatonit) crashes before establishing the network namespace. Any service using Podman pods is down until catatonit is downgraded.

      Please provide the package NVR for which the bug is seen:

      catatonit-0.2.1-3.el10.x86_64

      Also affects catatonit-0.2.1-2.el10.x86_64. The previous version catatonit-0.2.1-1.el10.x86_64 works correctly.

      How reproducible is this bug?

      100% — every invocation crashes.

      Steps to reproduce

      1. Install catatonit-0.2.1-3.el10 on CentOS Stream 10 x86_64
      2. Run /usr/libexec/podman/catatonit --version
      3. Observe segfault (exit code 139)

      Expected results

      catatonit --version prints its version string and exits 0. Podman pods start normally.

      Actual results

      catatonit segfaults before reaching main():

        $ /usr/libexec/podman/catatonit --version
        Segmentation fault (core dumped)
        $ echo $?
        139
        

      Kernel log:

        catatonit[3670]: segfault at a9b80 ip 00007f9c7f980dbb sp 00007fffac8dab80 error 4
          in catatonit[4dbb,7f9c7f97d000+77000] likely on CPU 0 (core 0, socket 0)
        

      Coredump stack trace:

        #0  0x00007f9c7f980dbb __libc_setup_tls (/usr/libexec/catatonit/catatonit + 0x4dbb)
        #1  0x00007f9c7f980a79 __libc_start_main_impl (/usr/libexec/catatonit/catatonit + 0x4a79)
        #2  0x00007f9c7f97e4e5 _start (/usr/libexec/catatonit/catatonit + 0x24e5)
        

      Binary info:

        $ file /usr/libexec/catatonit/catatonit
        ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), static-pie linked,
        BuildID[sha1]=e31fb3df4cb55aa2bb1abd1408bd7ec2e2270740, for GNU/Linux 3.2.0, stripped
        

      Environment:

        podman-5.8.0-2.el10.x86_64
        glibc-2.39-114.el10.x86_64
        kernel: 6.12.0-210.el10.x86_64 (also reproduced on 6.12.0-211.el10.x86_64)
        

      Workaround: dnf downgrade catatonit-0.2.1-1.el10

      Related: RHEL-152096 (the change that introduced -static-pie linking in 0.2.1-2)

              rhn-support-jnovy Jindrich Novy
              zacwest Zac West
              Container Runtime Eng Bot Container Runtime Eng Bot
              Container Runtime Bugs Bot Container Runtime Bugs Bot
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: