{"answers":{"affected":"It affects 11 products.","exploited":"There is no known exploitation of CVE-2025-0647 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-0647 is a high-severity vulnerability in Arm C1-Premium, published on 14 Jan 2026. 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-0647 and fix it if it is affected.\n\nWhat it is: CVE-2025-0647 is a high-severity vulnerability in Arm C1-Premium, published on 14 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-0647 in the wild and no public exploit code.\n\nAffected product: Arm C1-Premium. 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-0647/ (Markdown: https://insights.sbomify.com/CVE-2025-0647/index.md)","id":"CVE-2025-0647","markdown":"https://insights.sbomify.com/CVE-2025-0647/index.md","name":"CVE-2025-0647","record":{"aliases":["DEBIAN-CVE-2025-0647","GHSA-xxhx-7292-7rv8"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Arm CPU cores","requires_auth":"high_privilege","summary":"Attackers can exploit stale TLB entries in specific Arm CPUs to bypass memory isolation, potentially reading sensitive data or circumventing security controls.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Arm","cpe":[{"product":"c1-premium_firmware","vendor":"arm"},{"product":"c1-ultra_firmware","vendor":"arm"},{"product":"cortex-a710_firmware","vendor":"arm"},{"product":"cortex-x2_firmware","vendor":"arm"},{"product":"cortex-x3_firmware","vendor":"arm"},{"product":"cortex-x4_firmware","vendor":"arm"},{"product":"cortex-x925_firmware","vendor":"arm"},{"product":"neoverse-n2_firmware","vendor":"arm"},{"product":"neoverse-v2_firmware","vendor":"arm"},{"product":"neoverse-v3_firmware","vendor":"arm"},{"product":"neoverse-v3ae_firmware","vendor":"arm"}],"cvss":{"score":7.9,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-226","name":"Sensitive Information in Resource Not Removed Before Reuse"}],"description":"In certain Arm CPUs, a CPP RCTX instruction executed on one Processing Element (PE) may inhibit TLB invalidation when a TLBI is issued to the PE, either by the same PE or another PE in the shareability domain. In this case, the PE may retain stale TLB entries which should have been invalidated by the TLBI.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Other in C1-Premium","id":"CVE-2025-0647","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"M-Files Server crash via EOT database driver configuration","id":"CVE-2025-0648"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-0646"},"products":["C1-Premium","C1-Ultra","Cortex-A710","Cortex-X2","Cortex-X3","Cortex-X4","Cortex-X925","Neoverse-N2","Neoverse-V2","Neoverse-V3","Neoverse-V3AE"],"published":"2026-01-14","related":[{"cvss_score":5.1,"headline":"Information disclosure in C1-Premium","id":"CVE-2024-7881","kev_date_added":null,"published":"2025-01-28"}],"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-20","vendors":["Arm"]},"summary":"Attackers can exploit stale TLB entries in specific Arm CPUs to bypass memory isolation, potentially reading sensitive data or circumventing security controls.","url":"https://insights.sbomify.com/CVE-2025-0647/"}