{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-31316 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-31316 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-31316 is a high-severity vulnerability in AMD Instinct™ MI210, published on 15 May 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-2023-31316 and fix it if it is affected.\n\nWhat it is: CVE-2023-31316 is a high-severity vulnerability in AMD Instinct™ MI210, published on 15 May 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-2023-31316 in the wild and no public exploit code.\n\nAffected product: AMD Instinct™ MI210. 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-2023-31316/ (Markdown: https://insights.sbomify.com/CVE-2023-31316/index.md)","id":"CVE-2023-31316","markdown":"https://insights.sbomify.com/CVE-2023-31316/index.md","name":"CVE-2023-31316","record":{"aliases":["GHSA-xm8p-xfwc-w7p6"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","data_read","data_modify","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AMD Secure Processor","requires_auth":"low_privilege","summary":"An attacker with write access outside trusted memory can alter VCN firmware execution flow, compromising confidentiality, integrity, and availability of AMD hardware.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMD","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L","version":"4.0"},"cwes":[{"id":"CWE-1304","name":"Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation"}],"description":"Improperly preserved integrity of hardware configuration state during a power save/restore operation in the AMD Secure Processor (ASP) could allow an attacker with the ability to write outside the trusted memory range (TMR) to change the execution flow of the Video Core Next (VCN) firmware potentially impacting confidentiality, integrity, or availability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Other in AMD Instinct™ MI210","id":"CVE-2023-31316","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in AMD Instinct™ MI210","id":"CVE-2023-31317"},"packages":[],"prev":{"headline":"Code injection in 1st Gen AMD EPYC™ Processors","id":"CVE-2023-31315"},"products":["AMD Instinct™ MI210","AMD Instinct™ MI250","AMD Radeon™ PRO V620","AMD Radeon™ PRO W6000 Series Graphics Products","AMD Radeon™ PRO W7000 Series Graphics Products","AMD Radeon™ RX 6000 Series Graphics Products","AMD Radeon™ RX 7000 Series Graphics Products","AMD Ryzen™ 4000 Series Desktop Processors","AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics","AMD Ryzen™ 5000 Series Desktop Processors with Radeon™ Graphics","AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics","AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics","AMD Ryzen™ 7000 Series Desktop Processors","AMD Ryzen™ 7020 Series Processors with Radeon™ Graphics","AMD Ryzen™ 7040 Series Mobile Processors with Radeon™ Graphics","AMD Ryzen™ 7045 Series Mobile Processors with Radeon™ Graphics","AMD Ryzen™ Embedded V2000 Series Processors","AMD Ryzen™ Embedded V3000 Series Processors"],"published":"2026-05-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-05-15","vendors":["AMD"]},"summary":"An attacker with write access outside trusted memory can alter VCN firmware execution flow, compromising confidentiality, integrity, and availability of AMD hardware.","url":"https://insights.sbomify.com/CVE-2023-31316/"}