Canonical Apport: attackers can read data they should not see
OFFICIAL NAME: Race Condition in Canonical Apport
DO THIS FIRSTFind out if you use it. If you do, apply the vendor's fix. Not sure if you use it? Send this page to your IT provider or security lead and ask.
TECHNICAL SUMMARY 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…
WHY THIS VERDICT Attacks are reported but not confirmed by an authoritative source, and the vulnerability is more than 90 days old.
WHY IT RANKS HERE Exploitation is reported. The first report is 7 days old.
- HIGHEST CONFIRMED RUNG
- NOTHING YET
- CISA KEV
- NOT YET
- EXPLOIT CODE
- PROOF OF CONCEPT
How far has it climbed?
01 TALK
□ NO EVIDENCE YETNEWEST EVIDENCE NONE YETNo evidence yet.
SRC: NONE YET02 EXPOSED
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETWe have no source that counts exposed systems yet. Internet scan data needs a partnership we do not have. No evidence here does not mean nothing is exposed.
03 TRIED
▨ REPORTED, NOT CONFIRMEDNEWEST EVIDENCE · 1 SOURCEAttacks that worked are reported (step 4), so attempts count as reported too.
04 EXPLOITED
▨ REPORTED, NOT CONFIRMEDNEWEST EVIDENCE · 1 SOURCEExploitation of CVE-2025-5054 reported (CIRCL sighting).
05 DAMAGE
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETBreach notices and filings rarely name the flaw that was used, so we cannot link them to this event yet. No evidence here does not mean no harm.
When each thing happened
- DISCLOSED
- EXPLOIT CODE PUBLICDATE UNKNOWN
- FIRST ATTACK REPORT
- CISA KEV LISTINGNOT YET
- US FEDERAL DEADLINENOT YET
Questions to ask this week
- Do we run Canonical Apport? If yes, is it patched or cut off from the internet?
- Who owns fixing it, and by what date?
- Have we checked for signs of attack since the first report, not just since the patch?
How it unfolded
- MAY 30, 2025CISA Vulnrichment notes a public proof of concept for CVE-2025-5054
- JUN 5, 20251 public GitHub repository claims a proof of concept for CVE-2025-5054
- Attack activity. NOV 4, 2026Exploitation of CVE-2025-5054 reported (CIRCL sighting)
SOURCES
- [1] CIRCL Vulnerability-Lookup sightings: Exploitation of CVE-2025-5054 reported (CIRCL sighting), NOV 4
- [2] PoC-in-GitHub: 1 public GitHub repository claims a proof of concept for CVE-2025-5054, JUN 5
- [3] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment notes a public proof of concept for CVE-2025-5054, MAY 30