{"containers": {"cna": {"affected": [{"product": "xen", "vendor": "Xen", "versions": [{"status": "affected", "version": "4.13.x"}]}, {"product": "xen", "vendor": "Xen", "versions": [{"status": "affected", "version": "4.14.x"}]}, {"product": "xen", "vendor": "Xen", "versions": [{"status": "affected", "version": "4.15.x"}]}, {"product": "xen", "vendor": "Xen", "versions": [{"status": "affected", "version": "xen-unstable"}]}, {"product": "xen", "vendor": "Xen", "versions": [{"status": "affected", "version": "4.12.x"}]}, {"product": "xen", "vendor": "Xen", "versions": [{"status": "affected", "version": "4.11.x"}]}], "credits": [{"lang": "en", "value": "{'credit_data': {'description': {'description_data': [{'lang': 'eng', 'value': 'This issue was discovered by Igor Druzhinin and Andrew Cooper of Citrix,\\nand further issues were uncovered by by Jan Beulich of SUSE while trying\\nto fix the first issue.'}]}}}"}], "descriptions": [{"lang": "en", "value": "inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded."}], "metrics": [{"other": {"content": {"description": {"description_data": [{"lang": "eng", "value": "A malicious guest may be able to elevate its privileges to that of the\nhost, cause host or guest Denial of Service (DoS), or cause information\nleaks."}]}}, "type": "unknown"}}], "problemTypes": [{"descriptions": [{"description": "unknown", "lang": "en", "type": "text"}]}], "providerMetadata": {"dateUpdated": "2021-07-12T04:06:19", "orgId": "23aa2041-22e1-471f-9209-9b7396fa234f", "shortName": "XEN"}, "references": [{"tags": ["x_refsource_MISC"], "url": "https://xenbits.xenproject.org/xsa/advisory-373.txt"}, {"name": "GLSA-202107-30", "tags": ["vendor-advisory", "x_refsource_GENTOO"], "url": "https://security.gentoo.org/glsa/202107-30"}], "x_legacyV4Record": {"CVE_data_meta": {"ASSIGNER": "security@xen.org", "ID": "CVE-2021-28692", "STATE": "PUBLIC"}, "affects": {"vendor": {"vendor_data": [{"product": {"product_data": [{"product_name": "xen", "version": {"version_data": [{"version_value": "4.13.x"}]}}, {"product_name": "xen", "version": {"version_data": [{"version_value": "4.14.x"}]}}, {"product_name": "xen", "version": {"version_data": [{"version_value": "4.15.x"}]}}, {"product_name": "xen", "version": {"version_data": [{"version_value": "xen-unstable"}]}}, {"product_name": "xen", "version": {"version_data": [{"version_value": "4.12.x"}]}}, {"product_name": "xen", "version": {"version_data": [{"version_value": "4.11.x"}]}}]}, "vendor_name": "Xen"}]}}, "configuration": {"configuration_data": {"description": {"description_data": [{"lang": "eng", "value": "All Xen versions from at least 3.2 onwards are vulnerable. Earlier\nversions have not been inspected.\n\nOnly x86 systems with in-use IOMMU hardware are vulnerable. x86 systems\nwithout any IOMMUs in use are not vulnerable. On Arm systems IOMMU /\nSMMU use is not security supported.\n\nOnly x86 guests which have physical devices passed through to them can\nleverage the vulnerability."}]}}}, "credit": {"credit_data": {"description": {"description_data": [{"lang": "eng", "value": "This issue was discovered by Igor Druzhinin and Andrew Cooper of Citrix,\nand further issues were uncovered by by Jan Beulich of SUSE while trying\nto fix the first issue."}]}}}, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": {"description_data": [{"lang": "eng", "value": "inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded."}]}, "impact": {"impact_data": {"description": {"description_data": [{"lang": "eng", "value": "A malicious guest may be able to elevate its privileges to that of the\nhost, cause host or guest Denial of Service (DoS), or cause information\nleaks."}]}}}, "problemtype": {"problemtype_data": [{"description": [{"lang": "eng", "value": "unknown"}]}]}, "references": {"reference_data": [{"name": "https://xenbits.xenproject.org/xsa/advisory-373.txt", "refsource": "MISC", "url": "https://xenbits.xenproject.org/xsa/advisory-373.txt"}, {"name": "GLSA-202107-30", "refsource": "GENTOO", "url": "https://security.gentoo.org/glsa/202107-30"}]}, "workaround": {"workaround_data": {"description": {"description_data": [{"lang": "eng", "value": "Not passing through physical devices to untrusted guests will avoid\nthe vulnerability."}]}}}}}, "adp": [{"providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-08-03T21:47:33.190Z"}, "title": "CVE Program Container", "references": [{"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://xenbits.xenproject.org/xsa/advisory-373.txt"}, {"name": "GLSA-202107-30", "tags": ["vendor-advisory", "x_refsource_GENTOO", "x_transferred"], "url": "https://security.gentoo.org/glsa/202107-30"}]}]}, "cveMetadata": {"assignerOrgId": "23aa2041-22e1-471f-9209-9b7396fa234f", "assignerShortName": "XEN", "cveId": "CVE-2021-28692", "datePublished": "2021-06-30T10:27:57", "dateReserved": "2021-03-18T00:00:00", "dateUpdated": "2024-08-03T21:47:33.190Z", "state": "PUBLISHED"}, "dataType": "CVE_RECORD", "dataVersion": "5.1"}

{}

{"configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:o:xen:xen:*:*:*:*:*:*:*:*", "matchCriteriaId": "70FF936F-CF3F-4124-AF44-DAFE2D227F11", "versionStartIncluding": "3.2.0", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "inappropriate x86 IOMMU timeout detection / handling IOMMUs process commands issued to them in parallel with the operation of the CPU(s) issuing such commands. In the current implementation in Xen, asynchronous notification of the completion of such commands is not used. Instead, the issuing CPU spin-waits for the completion of the most recently issued command(s). Some of these waiting loops try to apply a timeout to fail overly-slow commands. The course of action upon a perceived timeout actually being detected is inappropriate: - on Intel hardware guests which did not originally cause the timeout may be marked as crashed, - on AMD hardware higher layer callers would not be notified of the issue, making them continue as if the IOMMU operation succeeded."}, {"lang": "es", "value": "Una detecci\u00f3n/manipulaci\u00f3n inapropiada del tiempo de espera de la IOMMU x86 Las IOMMUs procesan los comandos emitidos a ellas en paralelo con la operaci\u00f3n de la(s) CPU(s) que emiten dichos comandos. En la implementaci\u00f3n actual en Xen, la notificaci\u00f3n as\u00edncrona de la finalizaci\u00f3n de dichos comandos no es usada. En su lugar, la CPU emisora espera la finalizaci\u00f3n de la(s) \u00faltima(s) orden(es) emitida(s). Algunos de estos bucles de espera intentan aplicar un tiempo de espera para crear un fallo en los comandos demasiado lentos. El curso de acci\u00f3n cuando se detecta un tiempo de espera es inapropiado: - en el hardware de Intel los hu\u00e9spedes que no causaron originalmente el tiempo de espera pueden ser marcados como bloqueados, - en el hardware de AMD los llamadores de la capa superior no ser\u00edan notificados del problema, haci\u00e9ndolos continuar como si la operaci\u00f3n de IOMMU tuviera \u00e9xito"}], "id": "CVE-2021-28692", "lastModified": "2021-07-12T14:53:51.553", "metrics": {"cvssMetricV2": [{"acInsufInfo": false, "baseSeverity": "MEDIUM", "cvssData": {"accessComplexity": "LOW", "accessVector": "LOCAL", "authentication": "NONE", "availabilityImpact": "COMPLETE", "baseScore": 5.6, "confidentialityImpact": "PARTIAL", "integrityImpact": "NONE", "vectorString": "AV:L/AC:L/Au:N/C:P/I:N/A:C", "version": "2.0"}, "exploitabilityScore": 3.9, "impactScore": 7.8, "obtainAllPrivilege": false, "obtainOtherPrivilege": false, "obtainUserPrivilege": false, "source": "nvd@nist.gov", "type": "Primary", "userInteractionRequired": false}], "cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "baseScore": 7.1, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H", "version": "3.1"}, "exploitabilityScore": 1.8, "impactScore": 5.2, "source": "nvd@nist.gov", "type": "Primary"}]}, "published": "2021-06-30T11:15:08.087", "references": [{"source": "security@xen.org", "tags": ["Mitigation", "Third Party Advisory"], "url": "https://security.gentoo.org/glsa/202107-30"}, {"source": "security@xen.org", "tags": ["Vendor Advisory"], "url": "https://xenbits.xenproject.org/xsa/advisory-373.txt"}], "sourceIdentifier": "security@xen.org", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-269"}], "source": "nvd@nist.gov", "type": "Primary"}]}

{}