References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [email protected].

Change History

In the Linux kernel, the following vulnerability has been resolved:

iommu/amd: move wait_on_sem() out of spinlock

With iommu.strict=1, the existing completion wait path can cause soft
lockups under stressed environment, as wait_on_sem() busy-waits under the
spinlock with interrupts disabled.

Move the completion wait in iommu_completion_wait() out of the spinlock.
wait_on_sem() only polls the hardware-updated cmd_sem and does not require
iommu->lock, so holding the lock during the busy wait unnecessarily
increases contention and extends the time with interrupts disabled.

https://git.kernel.org/stable/c/496269d12072ecb219826485bdbec70c92a8eef5

https://git.kernel.org/stable/c/715c263119fd1b918a9fcbd8a36ea5b604a46324

https://git.kernel.org/stable/c/d2a0cac10597068567d336e85fa3cbdbe8ca62bf

https://git.kernel.org/stable/c/e15768e68820142077bbca402d8e902f64ade1b0

https://git.kernel.org/stable/c/f2f65b28d802a667119147444ec2ae33eebf9a58