{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-45818 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-45818 is a medium-severity denial of service vulnerability in Xen Xen, published on 19 Dec 2024. 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-2024-45818 and fix it if it is affected.\n\nWhat it is: CVE-2024-45818 is a medium-severity denial of service vulnerability in Xen Xen, published on 19 Dec 2024. 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-2024-45818 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-2024-45818/ (Markdown: https://insights.sbomify.com/CVE-2024-45818/index.md)","id":"CVE-2024-45818","markdown":"https://insights.sbomify.com/CVE-2024-45818/index.md","name":"CVE-2024-45818","record":{"aliases":["ALPINE-CVE-2024-45818","DEBIAN-CVE-2024-45818","GHSA-9ppw-wh7x-2qc9","UBUNTU-CVE-2024-45818"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Xen hypervisor","requires_auth":"low_privilege","summary":"A deadlock in Xen hypervisor VGA handling allows guest users to cause a denial of service by triggering specific memory access patterns.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"XEN","cpe":[{"product":"xen","vendor":"xen"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-667","name":"Improper Locking"}],"description":"The hypervisor contains code to accelerate VGA memory accesses for HVM\nguests, when the (virtual) VGA is in \"standard\" mode.  Locking involved\nthere has an unusual discipline, leaving a lock acquired past the\nreturn from the function that acquired it.  This behavior results in a\nproblem when emulating an instruction with two memory accesses, both of\nwhich touch VGA memory (plus some further constraints which aren't\nrelevant here).  When emulating the 2nd access, the lock that is already\nbeing held would be attempted to be re-acquired, resulting in a\ndeadlock.\n\nThis deadlock was already found when the code was first introduced, but\nwas analysed incorrectly and the fix was incomplete.  Analysis in light\nof the new finding cannot find a way to make the existing locking\ndiscipline work.\n\nIn staging, this logic has all been removed because it was discovered\nto be accidentally disabled since Xen 4.7.  Therefore, we are fixing the\nlocking problem by backporting the removal of most of the feature.  Note\nthat even with the feature disabled, the lock would still be acquired\nfor any accesses to the VGA MMIO region.","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":"Deadlock in x86 HVM standard VGA handling","id":"CVE-2024-45818","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"xen:xen","products":["xen:xen"],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"libxl leaks data to PVH guests via ACPI tables","id":"CVE-2024-45819"},"packages":[],"prev":{"headline":"x86: Deadlock in vlapic_error()","id":"CVE-2024-45817"},"products":["Xen"],"published":"2024-12-19","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":"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":"partial"},"state":"PUBLISHED","updated":"2024-12-31","vendors":["Xen"]},"summary":"A deadlock in Xen hypervisor VGA handling allows guest users to cause a denial of service by triggering specific memory access patterns.","url":"https://insights.sbomify.com/CVE-2024-45818/"}