CVE-2025-5054: Race Condition in Canonical Apport

NVD analysis

Status

Modified

Published

2025-05-30T18:15:32.670

Last modified

2026-06-17T09:47:06.343

Weaknesses

CWE-362

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).

References

• https://ubuntu.com/security/CVE-2025-5054 (Third Party Advisory)
• https://ubuntu.com/security/notices/USN-7545-1 (Third Party Advisory)
• https://www.qualys.com/2025/05/29/apport-coredump/apport-coredump.txt (Exploit, Mitigation, Third Party Advisory)
• http://seclists.org/fulldisclosure/2025/Jun/9

This product uses the NVD API but is not endorsed or certified by the NVD.

Read on 2026-11-03T01:45:30.693Z under licence nvd-api-terms-of-use@ff2a5288 from https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2025-5054

CVE record

Title (CNA)

Race Condition in Canonical Apport

Assigner

canonical

State

PUBLISHED

Published

2025-05-30T17:37:01.006Z

Updated

2025-11-03T20:05:43.609Z

Problem types

CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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).

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

Read on 2026-11-03T02:17:03.176Z under licence cve-terms-of-use@81bfa2f3 from https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2025/5xxx/CVE-2025-5054.json

Detection rules (SigmaHQ)

SigmaHQ rules whose own tags name this CVE. Each rule page shows the rule as its author published it.

• Potential Exploitation of CVE-2025-5054 or CVE-2025-4598 (status experimental, level medium)

Defensive techniques (MITRE D3FEND)

D3FEND maps these defensive techniques to the weakness (CWE) that NVD lists for this CVE, through the digital artifacts the weakness affects. D3FEND does not say they stop this vulnerability.

MITRE D3FEND™ knowledge graph. © 2025 The MITRE Corporation.
"The MITRE Corporation (MITRE) hereby grants you a non-exclusive, royalty-free license to use D3FEND for research, development, and commercial purposes. Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy." Terms: https://d3fend.mitre.org/tou/