What is CVE-2025-5054?A medium-severity flaw in Apport, explained.
CVE-2025-5054 is a medium-severity flaw (CVSS 4.7) in Apport from Canonical, published on 30 May 2025. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.8%. If you run an affected version, plan in the vendor’s fix.
Published 30 May 2025. Record last updated 22 August 2025. We keep this page's data up to date.
What is CVE-2025-5054? In plain terms.
An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data.
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 kind of flaw is it?
- CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAlready on the device
- How hard it is to pull offHard: conditions must line up
- Login needed firstAn ordinary user account
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data
Severity vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Is CVE-2025-5054 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.8%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2025-5054 scores 36. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isKey context
- Real threat activity around itKey context
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2025-5054 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2025-5054? 2 products.
The published record lists 2 products from 1 vendor. If you run one of these, check your version, then go to the fix below.
- Application
Apport
by Canonical
Affected versionsup to 2.32.0 - Operating system
Ubuntu Linux
by Canonical
Affected versions16.0418.0420.0422.0424.0424.1025.04
How do I fix CVE-2025-5054? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? EdgeProtect can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2025-5054 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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. W...
- Matched to
- Apport on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2025-5054 is a medium-severity flaw in Apport from Canonical, published on 30 May 2025. An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data.
It scores 4.7 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2025-5054 is 36 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.8%. That can change at any time, which is why we keep watching.
For Apport from Canonical: up to 2.32.0. The record lists 2 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.