CVE-2025-5054: medium-severity vulnerability in Canonical Apport
Race Condition in Canonical Apport
Published · Updated
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.7epss 0.8%
exploitation probability
0.8%top 46% of all CVEs
observed exploitation
nono source reports it
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).
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Affected products
Canonical · ApportRelated CVEs — Canonical Apport
In the same product, most dangerous first.
CVE-2020-8831MEDIUMWorld writable root owned lock file created in user controllable locationEPSS 0.7%CVE-2019-15790LOWApport reads PID files with elevated privilegesEPSS 0.5%CVE-2020-8833MEDIUMApport race condition in crash report permissionsEPSS 0.3%CVE-2026-77113MEDIUMPath Traversal Vulnerability in apport-unpackEPSS 0.2%