Answer in brief
CVE-2026-43253 records a High severity (CVSS 7.5) vulnerability in iommu/amd: move wait_on_sem() out of spinlock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4bf5beef578e46393f11eb69dda7d17a065e05ff <f2f65b28d802a667119147444ec2ae33eebf9a58 || >=4bf5beef578e46393f11eb69dda7d17a065e05ff <715c263119fd1b918a9fcbd8a36ea5b604a46324 || >=4bf5beef578e46393f11eb69dda7d17a065e05ff <e15768e68820142077bbca402d8e902f64ade1b0 || >=4bf5beef578e46393f11eb69dda7d17a065e05ff <496269d12072ecb219826485bdbec70c92a8eef5 || >=4bf5beef578e46393f11eb69dda7d17a065e05ff <d2a0cac10597068567d336e85fa3cbdbe8ca62bf | f2f65b28d802a667119147444ec2ae33eebf9a58, 715c263119fd1b918a9fcbd8a36ea5b604a46324, e15768e68820142077bbca402d8e902f64ade1b0, 496269d12072ecb219826485bdbec70c92a8eef5, d2a0cac10597068567d336e85fa3cbdbe8ca62bf |
| Linux/Linuxgeneric | 4.9 | Not reported |
| Linux/Linuxgeneric | >=4bf5beef578e46393f11eb69dda7d17a065e05ff <69d9339c02eddfc2a345be7220651068a3684383 || >=4bf5beef578e46393f11eb69dda7d17a065e05ff <f2f65b28d802a667119147444ec2ae33eebf9a58 || >=4bf5beef578e46393f11eb69dda7d17a065e05ff <715c263119fd1b918a9fcbd8a36ea5b604a46324 || >=4bf5beef578e46393f11eb69dda7d17a065e05ff <e15768e68820142077bbca402d8e902f64ade1b0 || >=4bf5beef578e46393f11eb69dda7d17a065e05ff <496269d12072ecb219826485bdbec70c92a8eef5 || >=4bf5beef578e46393f11eb69dda7d17a065e05ff <d2a0cac10597068567d336e85fa3cbdbe8ca62bf | 69d9339c02eddfc2a345be7220651068a3684383, f2f65b28d802a667119147444ec2ae33eebf9a58, 715c263119fd1b918a9fcbd8a36ea5b604a46324, e15768e68820142077bbca402d8e902f64ade1b0, 496269d12072ecb219826485bdbec70c92a8eef5, d2a0cac10597068567d336e85fa3cbdbe8ca62bf |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.