CVE-2025-5054
No known exploitation. EPSS puts it in the 55th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- Canonical ApportAffected: ≥ 2.20.1, < 2.20.1-0ubuntu2.30+esm5Upgrade to: 2.20.1-0ubuntu2.30+esm5Affected: ≥ 2.20.9, < 2.20.9-0ubuntu7.29+esm1Upgrade to: 2.20.9-0ubuntu7.29+esm1Affected: ≥ 2.20.11, < 2.20.11-0ubuntu27.28Upgrade to: 2.20.11-0ubuntu27.28Affected: ≥ 2.20.11, < 2.20.11-0ubuntu82.7Upgrade to: 2.20.11-0ubuntu82.7 + 5 more branchesStated by: CVE record
- Canonical Ltd. UbuntuAffected: 16.04 LTSUpgrade to: not statedStated by: BDU
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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).
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.8% chance of exploitation activity in the next 30 days, which ranks it in the 55th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
7 events over 391 days, from the signal feeds we watch.
- OpenVAS check added
- Patch availableworkaround available, record updated
- Publishedweakness classified, att&ck mapped
Affected products
And 3 more affected products. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Scored 4.7 by NVD.
How it is reached
- Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
- Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
- Privileges Required LowRequires basic user-level privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity NoneNo integrity impact
- Availability NoneNo availability impact
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Privilege EscalationT1068Exploitation for Privilege Escalationmedium confidence
Sources
References in the record
- ubuntu.com/security/notices/USN-7545-1
- ubuntu.com/security/CVE-2025-5054
- qualys.com/2025/05/29/apport-coredump/apport-coredump.txt
And 6 more references. See all after sign-in
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Apport, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI