{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-28690 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2021-28690 is a medium-severity vulnerability in Xen Xen, published on 29 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-28690 and fix it if it is affected.\n\nWhat it is: CVE-2021-28690 is a medium-severity vulnerability in Xen Xen, published on 29 Jun 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-28690 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-2021-28690/ (Markdown: https://insights.sbomify.com/CVE-2021-28690/index.md)","id":"CVE-2021-28690","markdown":"https://insights.sbomify.com/CVE-2021-28690/index.md","name":"CVE-2021-28690","record":{"aliases":["ALPINE-CVE-2021-28690","DEBIAN-CVE-2021-28690","GHSA-7qwx-5h4j-5c9w","UBUNTU-CVE-2021-28690"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Xen hypervisor","requires_auth":"low_privilege","summary":"Attackers can bypass TSX Async Abort mitigations after S3 suspend if TSX is disabled via non-default settings, exposing systems to speculative execution attacks.","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":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"x86: TSX Async Abort protections not restored after S3 This issue relates to the TSX Async Abort speculative security vulnerability. Please see https://xenbits.xen.org/xsa/advisory-305.html for details. Mitigating TAA by disabling TSX (the default and preferred option) requires selecting a non-default setting in MSR_TSX_CTRL. This setting isn't restored after S3 suspend.","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":"Security feature bypass in xen","id":"CVE-2021-28690","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"xen:xen","products":["xen:xen"],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Use after free in Linux","id":"CVE-2021-28691"},"packages":[],"prev":{"headline":"Information disclosure in Xen","id":"CVE-2021-28689"},"products":["xen"],"published":"2021-06-29","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Xen"]},"summary":"Attackers can bypass TSX Async Abort mitigations after S3 suspend if TSX is disabled via non-default settings, exposing systems to speculative execution attacks.","url":"https://insights.sbomify.com/CVE-2021-28690/"}