Skip to main content

CRE-2025-0139

Container exited 139 due to segmentation fault (SIGSEGV)Medium
Impact: 7/10
Mitigation: 2/10

CRE-2025-0139View on GitHub

Description

Exit code 139 indicates SIGSEGV (invalid memory access) in native/runtime code.

Frequently caused by unsafe pointer operations, ABI/library mismatches, or native extensions.


Cause

  • Null dereference or out-of-bounds access in C/C++/Rust unsafe blocks.
  • Incompatible glibc/musl or driver/library versions.
  • Faulty JNI/ctypes/native extension code paths.

Mitigation

  • Enable core dumps and symbol files; capture stack traces.
  • Pin compatible base image/libc; verify ABI expectations.
  • Use ASAN/UBSAN builds; bisect recent native/library changes.

References