iommu/amd: move wait_on_sem() out of spinlock
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4bf5beef578e46393f11eb69dda7d17a065e05ff · < d2a0cac10597068567d336e85fa3cbdbe8ca62bf| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s AMD IOMMU completion wait can cause soft lockups when iommu.strict=1 and the system is under stress. The wait busy-loops while holding a spinlock with interrupts disabled. The input does not specify an attacker, access requirements, or user interaction.
Operators running Linux kernels with AMD IOMMU should check their kernel vendor’s advisory for affected versions; none are listed in the input.