CVE-2026-43253
iommu/amd: move wait_on_sem() out of spinlock
Using Linux by Linux?
Get instant alerts when new vulnerabilities affect Linux - before attackers find them.
Description
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.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
- https://git.kernel.org/stable/c/f2f65b28d802a667119147444ec2ae33eebf9a58
- https://git.kernel.org/stable/c/715c263119fd1b918a9fcbd8a36ea5b604a46324
- https://git.kernel.org/stable/c/e15768e68820142077bbca402d8e902f64ade1b0
- https://git.kernel.org/stable/c/496269d12072ecb219826485bdbec70c92a8eef5
- https://git.kernel.org/stable/c/d2a0cac10597068567d336e85fa3cbdbe8ca62bf
References (5)
SSVC — Action Prioritization
SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.
CVSS
Quick Info
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.