{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-42336 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-42336 is a low-severity vulnerability in Xen Xen, published on 17 May 2023. 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-2022-42336 and fix it if it is affected.\n\nWhat it is: CVE-2022-42336 is a low-severity vulnerability in Xen Xen, published on 17 May 2023. 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-2022-42336 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-2022-42336/ (Markdown: https://insights.sbomify.com/CVE-2022-42336/index.md)","id":"CVE-2022-42336","markdown":"https://insights.sbomify.com/CVE-2022-42336/index.md","name":"CVE-2022-42336","record":{"aliases":["ALPINE-CVE-2022-42336","DEBIAN-CVE-2022-42336","GHSA-79pv-m8fc-mhfj","UBUNTU-CVE-2022-42336","openSUSE-SU-2024:12959-1"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Xen hypervisor","requires_auth":"low_privilege","summary":"Guests on AMD/Hygon hardware can bypass Spectre mitigations by underflowing the SSBD thread counter, disabling protections for other guests on the same core.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"XEN","cpe":[{"product":"xen","vendor":"xen"}],"cvss":{"score":3.3,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[],"description":"Mishandling of guest SSBD selection on AMD hardware The current logic to set SSBD on AMD Family 17h and Hygon Family 18h processors requires that the setting of SSBD is coordinated at a core level, as the setting is shared between threads. Logic was introduced to keep track of how many threads require SSBD active in order to coordinate it, such logic relies on using a per-core counter of threads that have SSBD active. When running on the mentioned hardware, it's possible for a guest to under or overflow the thread counter, because each write to VIRT_SPEC_CTRL.SSBD by the guest gets propagated to the helper that does the per-core active accounting. Underflowing the counter causes the value to get saturated, and thus attempts for guests running on the same core to set SSBD won't have effect because the hypervisor assumes it's already active.","ecosystems":["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":"Security feature bypass in xen","id":"CVE-2022-42336","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"xen:xen","products":["xen:xen"],"type":"security_feature_bypass","year":"2022"},"n_packages":1,"n_references":2,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2022-42337"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["4.17.1_04-1.1"],"introduced":["0"],"last_affected":[],"package":"xen","purl":"pkg:rpm/opensuse/xen\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:12959-1"}],"prev":{"headline":"Null dereference in xen","id":"CVE-2022-42335"},"products":["xen"],"published":"2023-05-17","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":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-22","vendors":["Xen"]},"summary":"Guests on AMD/Hygon hardware can bypass Spectre mitigations by underflowing the SSBD thread counter, disabling protections for other guests on the same core.","url":"https://insights.sbomify.com/CVE-2022-42336/"}