{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5054 exists.","fix":"Apply the vendor's patch.","what":"CVE-2025-5054 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 30 May 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-5054 and fix it if it is affected.\n\nWhat it is: CVE-2025-5054 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 30 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5054 exists.\n\nAffected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-5054/ (Markdown: https://insights.sbomify.com/CVE-2025-5054/index.md)","id":"CVE-2025-5054","markdown":"https://insights.sbomify.com/CVE-2025-5054/index.md","name":"CVE-2025-5054","record":{"aliases":["GHSA-4c8w-67qj-c8vp","UBUNTU-CVE-2025-5054","USN-7545-1"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ubuntu crash handler","requires_auth":"low_privilege","summary":"A local attacker can exploit a race condition in Canonical Apport to leak sensitive information by leveraging PID reuse and namespaces.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"canonical","cpe":[{"product":"apport","vendor":"canonical"},{"product":"ubuntu_linux","vendor":"canonical"}],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"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.\n\nWhen 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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-06-06","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-06-06T03:13:19Z","kind":"github_poc","ref":"https://github.com/daryllundy/cve-2025-5054","stars":2,"title":"Python tool to detect CVE-2025-5054 vulnerability in Ubuntu systems running Apport ≤ 2.32.0. Performs comprehensive security checks and provides mitigation recommendations."}],"tier":"weaponised"},"has_fix":true,"headline":"Race Condition in Canonical Apport","id":"CVE-2025-5054","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"canonical:ubuntu_linux","products":["canonical:ubuntu_linux"],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Smart Forms \u003c= 2.6.98 - Authenticated (Admin+) Stored Cross-Site Scripting","id":"CVE-2025-5055"},"packages":[],"prev":{"headline":"FreeFloat FTP Server MDIR Command buffer overflow","id":"CVE-2025-5053"},"products":["Apport"],"published":"2025-05-30","related":[{"cvss_score":8.8,"headline":"apport improperly parses /proc/pid/status","id":"CVE-2021-25682","kev_date_added":null,"published":"2021-06-11"},{"cvss_score":8.8,"headline":"apport improperly parses /proc/pid/stat","id":"CVE-2021-25683","kev_date_added":null,"published":"2021-06-11"},{"cvss_score":8.8,"headline":"apport can be stalled by reading a FIFO","id":"CVE-2021-25684","kev_date_added":null,"published":"2021-06-11"},{"cvss_score":7.8,"headline":"Race condition in Apport","id":"CVE-2021-3899","kev_date_added":null,"published":"2024-06-03"},{"cvss_score":7.8,"headline":"Other in Apport","id":"CVE-2022-1242","kev_date_added":null,"published":"2024-06-03"},{"cvss_score":7.7,"headline":"local privilege escalation in apport-cli","id":"CVE-2023-1326","kev_date_added":null,"published":"2023-04-13"},{"cvss_score":7.5,"headline":"Denial of service in Apport","id":"CVE-2022-28653","kev_date_added":null,"published":"2025-01-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-03","vendors":["Canonical"]},"summary":"A local attacker can exploit a race condition in Canonical Apport to leak sensitive information by leveraging PID reuse and namespaces.","url":"https://insights.sbomify.com/CVE-2025-5054/"}