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.
NOTE: The following CVSS v3.0 metrics and score provided are preliminary and subject to review.
|Base Score:||7.1||Base Metrics:||AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H|
|Access Vector:||Local network||Attack Complexity:||Low|
|Privileges Required:||Low||User Interaction:||None|
|Integrity Impact:||None||Availability Impact:||High|
|Oracle VM version 3 (xen)||OVMSA-2021-0020||2021-06-25|
This page is generated automatically and has not been checked for errors or omissions. For clarification or corrections please contact the Oracle Linux ULN team