cve.bz

CVE-2025-5054 canonical: Race Condition

4.7 mediumExploit referenceEPSS 0.8%

Medium (4.7) in canonical. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
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).

Severity

CVSS 3.1

4.7 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 57th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2025-05-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-5054 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-5054?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-5054?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-5054 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Canonical Apportfrom 2.20.1 before 2.20.1-0ubuntu2.30+esm5
Canonical Apportfrom 2.20.9 before 2.20.9-0ubuntu7.29+esm1
Canonical Apportfrom 2.20.11 before 2.20.11-0ubuntu27.28
Canonical Apportfrom 2.20.11 before 2.20.11-0ubuntu82.7
Canonical Apportfrom 2.28.1 before 2.28.1-0ubuntu3.6
Canonical Apportfrom 2.30.0 before 2.30.0-0ubuntu4.3
Canonical Apportfrom 2.32.0 before 2.32.0-0ubuntu5.1
Canonical Apportfrom 2.32.0 before 2.33.0-0ubuntu1
Canonical Apportfrom 2.20 through 2.32.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu20.04:LTSapport2.20.11-0ubuntu27.28UBUNTU-CVE-2025-5054 USN-7545-1
Ubuntu22.04:LTSapport2.20.11-0ubuntu82.7UBUNTU-CVE-2025-5054 USN-7545-1
Ubuntu24.04:LTSapport2.28.1-0ubuntu3.6UBUNTU-CVE-2025-5054 USN-7545-1
UbuntuPro:16.04:LTSapport2.20.1-0ubuntu2.30+esm5UBUNTU-CVE-2025-5054 USN-7545-1
UbuntuPro:18.04:LTSapport2.20.9-0ubuntu7.29+esm1UBUNTU-CVE-2025-5054 USN-7545-1

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON