First published: Wed Jun 30 2021(Updated: )
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.
Credit: security@xen.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/xen | 4.11.4+107-gef32c7afa2-1 4.14.6-1 4.14.5+94-ge49571868d-1 4.17.1+2-gb773c48e36-1 4.17.2+55-g0b56bed864-1 | |
Xen xen-unstable | >=3.2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-28692 has a medium severity rating due to potential impacts on system stability and security.
To fix CVE-2021-28692, upgrade the Xen package to a version equal to or greater than 4.11.4+107-gef32c7afa2-1 or any other patched version.
CVE-2021-28692 affects Xen versions starting from 3.2.0 up to the versions that have not been patched.
CVE-2021-28692 involves inappropriate timeout detection and handling in IOMMUs, which may lead to delays in command processing.
Currently, there are no recommended workarounds for CVE-2021-28692, and applying the security patch is essential for protection.