{"answers":{"affected":"It affects 23 products.","exploited":"There is no known exploitation of CVE-2021-26348 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2021-26348 is a medium-severity memory corruption vulnerability in Amd Epyc 72f3 Firmware, published on 11 May 2022. 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-2021-26348 and fix it if it is affected.\n\nWhat it is: CVE-2021-26348 is a medium-severity memory corruption vulnerability in Amd Epyc 72f3 Firmware, published on 11 May 2022. 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-2021-26348 in the wild and no public exploit code.\n\nAffected product: Amd Epyc 72f3 Firmware. 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-26348/ (Markdown: https://insights.sbomify.com/CVE-2021-26348/index.md)","id":"CVE-2021-26348","markdown":"https://insights.sbomify.com/CVE-2021-26348/index.md","name":"CVE-2021-26348","record":{"aliases":["GHSA-8563-gc3w-c38p"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AMD EPYC Processors","requires_auth":"low_privilege","summary":"An IOMMU TLB flush failure allows IO devices to write to unauthorized memory, compromising system integrity on AMD EPYC processors.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMD","cpe":[{"product":"epyc_72f3_firmware","vendor":"amd"},{"product":"epyc_7313_firmware","vendor":"amd"},{"product":"epyc_7313p_firmware","vendor":"amd"},{"product":"epyc_7343_firmware","vendor":"amd"},{"product":"epyc_7373x_firmware","vendor":"amd"},{"product":"epyc_73f3_firmware","vendor":"amd"},{"product":"epyc_7413_firmware","vendor":"amd"},{"product":"epyc_7443_firmware","vendor":"amd"},{"product":"epyc_7443p_firmware","vendor":"amd"},{"product":"epyc_7453_firmware","vendor":"amd"},{"product":"epyc_7473x_firmware","vendor":"amd"},{"product":"epyc_74f3_firmware","vendor":"amd"},{"product":"epyc_7513_firmware","vendor":"amd"},{"product":"epyc_7543_firmware","vendor":"amd"},{"product":"epyc_7543p_firmware","vendor":"amd"},{"product":"epyc_7573x_firmware","vendor":"amd"},{"product":"epyc_75f3_firmware","vendor":"amd"},{"product":"epyc_7643_firmware","vendor":"amd"},{"product":"epyc_7663_firmware","vendor":"amd"},{"product":"epyc_7713_firmware","vendor":"amd"},{"product":"epyc_7713p_firmware","vendor":"amd"},{"product":"epyc_7763_firmware","vendor":"amd"},{"product":"epyc_7773x_firmware","vendor":"amd"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"Failure to flush the Translation Lookaside Buffer (TLB) of the I/O memory management unit (IOMMU) may lead an IO device to write to memory it should not be able to access, resulting in a potential loss of integrity.","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":"Memory corruption in EPYC™ Processors","id":"CVE-2021-26348","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"amd:epyc_72f3_firmware","products":["amd:epyc_72f3_firmware","amd:epyc_7313_firmware","amd:epyc_7313p_firmware","amd:epyc_7343_firmware","amd:epyc_7373x_firmware","amd:epyc_73f3_firmware","amd:epyc_7413_firmware","amd:epyc_7443_firmware","amd:epyc_7443p_firmware","amd:epyc_7453_firmware","amd:epyc_7473x_firmware","amd:epyc_74f3_firmware","amd:epyc_7513_firmware","amd:epyc_7543_firmware","amd:epyc_7543p_firmware","amd:epyc_7573x_firmware","amd:epyc_75f3_firmware","amd:epyc_7643_firmware","amd:epyc_7663_firmware","amd:epyc_7713_firmware","amd:epyc_7713p_firmware","amd:epyc_7763_firmware","amd:epyc_7773x_firmware"],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in EPYC™ Processors","id":"CVE-2021-26349"},"packages":[],"prev":{"headline":"Integer overflow in Ryzen 5000 Series","id":"CVE-2021-26347"},"products":["EPYC™ Processors"],"published":"2022-05-11","related":[{"cvss_score":7.8,"headline":"Memory corruption in 3rd Gen AMD EPYC™","id":"CVE-2021-26324","kev_date_added":null,"published":"2022-05-10"},{"cvss_score":7.8,"headline":"Memory corruption in 3rd Gen EPYC","id":"CVE-2021-26353","kev_date_added":null,"published":"2022-05-10"},{"cvss_score":7.8,"headline":"Other in 3rd Gen AMD EPYC™","id":"CVE-2021-46771","kev_date_added":null,"published":"2022-05-10"},{"cvss_score":7.5,"headline":"Other in 3rd Gen AMD EPYC™","id":"CVE-2022-23818","kev_date_added":null,"published":"2023-05-09"},{"cvss_score":7.1,"headline":"Memory corruption in 3rd Gen AMD EPYC™","id":"CVE-2021-26397","kev_date_added":null,"published":"2023-05-09"},{"cvss_score":7.1,"headline":"Other in 3rd Gen AMD EPYC™","id":"CVE-2021-26332","kev_date_added":null,"published":"2022-05-10"},{"cvss_score":5.5,"headline":"Denial of service in Athlon™ Series","id":"CVE-2021-26339","kev_date_added":null,"published":"2022-05-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-09-16","vendors":["AMD"]},"summary":"An IOMMU TLB flush failure allows IO devices to write to unauthorized memory, compromising system integrity on AMD EPYC processors.","url":"https://insights.sbomify.com/CVE-2021-26348/"}