{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-58149 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-58149 is a high-severity missing authorization vulnerability in Xen Xen, published on 31 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-58149 and fix it if it is affected.\n\nWhat it is: CVE-2025-58149 is a high-severity missing authorization vulnerability in Xen Xen, published on 31 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-58149 in the wild and no public exploit code.\n\nAffected product: Xen Xen. 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-58149/ (Markdown: https://insights.sbomify.com/CVE-2025-58149/index.md)","id":"CVE-2025-58149","markdown":"https://insights.sbomify.com/CVE-2025-58149/index.md","name":"CVE-2025-58149","record":{"aliases":["ALPINE-CVE-2025-58149","DEBIAN-CVE-2025-58149","GHSA-38qg-7h9q-7h29","SUSE-SU-2025:4419-1","SUSE-SU-2025:4490-1","UBUNTU-CVE-2025-58149","openSUSE-SU-2025:15719-1"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Xen hypervisor","requires_auth":"none","summary":"Attackers can retain access to 64-bit memory BARs after PCI device unplug, allowing unauthorized memory mapping and potential privilege escalation.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"XEN","cpe":[{"product":"xen","vendor":"xen"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-672","name":"Operation on a Resource after Expiration or Release"}],"description":"When passing through PCI devices, the detach logic in libxl won't remove\naccess permissions to any 64bit memory BARs the device might have.  As a\nresult a domain can still have access any 64bit memory BAR when such\ndevice is no longer assigned to the domain.\n\nFor PV domains the permission leak allows the domain itself to map the memory\nin the page-tables.  For HVM it would require a compromised device model or\nstubdomain to map the leaked memory into the HVM domain p2m.","ecosystems":["SUSE:Linux Enterprise Micro 5.5","SUSE:Linux Enterprise Module for Basesystem 15 SP7","SUSE:Linux Enterprise Module for Server Applications 15 SP7","openSUSE:Tumbleweed"],"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":"Incorrect removal of permissions on PCI device unplug","id":"CVE-2025-58149","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"xen:xen","products":["xen:xen"],"type":"missing_authorization","year":"2025"},"n_packages":4,"n_references":1,"next":{"headline":"x86: buffer overrun with shadow paging + tracing","id":"CVE-2025-58150"},"packages":[{"ecosystem":"SUSE:Linux Enterprise Micro 5.5","fixed":["4.17.6_02-150500.3.56.1"],"introduced":["0"],"last_affected":[],"package":"xen","purl":"pkg:rpm/suse/xen\u0026distro=SUSE%20Linux%20Enterprise%20Micro%205.5","source":"SUSE-SU-2025:4490-1"},{"ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","fixed":["4.20.2_02-150700.3.19.1"],"introduced":["0"],"last_affected":[],"package":"xen","purl":"pkg:rpm/suse/xen\u0026distro=SUSE%20Linux%20Enterprise%20Module%20for%20Basesystem%2015%20SP7","source":"SUSE-SU-2025:4419-1"},{"ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP7","fixed":["4.20.2_02-150700.3.19.1"],"introduced":["0"],"last_affected":[],"package":"xen","purl":"pkg:rpm/suse/xen\u0026distro=SUSE%20Linux%20Enterprise%20Module%20for%20Server%20Applications%2015%20SP7","source":"SUSE-SU-2025:4419-1"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["4.20.1_08-1.1"],"introduced":["0"],"last_affected":[],"package":"xen","purl":"pkg:rpm/opensuse/xen\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2025:15719-1"}],"prev":{"headline":"x86: Incorrect input sanitisation in Viridian hypercalls","id":"CVE-2025-58148"},"products":["Xen"],"published":"2025-10-31","related":[{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2017-10912","kev_date_added":null,"published":"2017-07-05"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2017-10918","kev_date_added":null,"published":"2017-07-05"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2017-10920","kev_date_added":null,"published":"2017-07-05"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2017-10921","kev_date_added":null,"published":"2017-07-05"},{"cvss_score":9.8,"headline":"Mutiple vulnerabilities in the Viridian interface","id":"CVE-2025-27466","kev_date_added":null,"published":"2025-09-11"},{"cvss_score":9.8,"headline":"Mutiple vulnerabilities in the Viridian interface","id":"CVE-2025-58142","kev_date_added":null,"published":"2025-09-11"},{"cvss_score":9.8,"headline":"Mutiple vulnerabilities in the Viridian interface","id":"CVE-2025-58143","kev_date_added":null,"published":"2025-09-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"SUSE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-04","vendors":["Xen"]},"summary":"Attackers can retain access to 64-bit memory BARs after PCI device unplug, allowing unauthorized memory mapping and potential privilege escalation.","url":"https://insights.sbomify.com/CVE-2025-58149/"}