CVE-2026-43220

iommu/amd: serialize sequence allocation under concurrent TLB invalidations

Published May 6, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

iommu/amd: serialize sequence allocation under concurrent TLB invalidations

With concurrent TLB invalidations, completion wait randomly gets timed out
because cmd_sem_val was incremented outside the IOMMU spinlock, allowing
CMD_COMPL_WAIT commands to be queued out of sequence and breaking the
ordering assumption in wait_on_sem().
Move the cmd_sem_val increment under iommu->lock so completion sequence
allocation is serialized with command queuing.
And remove the unnecessary return.

Analysis

AI-generated

Technical impact

An AMD IOMMU driver race condition in the Linux kernel serializes CMD_COMPL_WAIT command sequencing incorrectly due to incrementing cmd_sem_val outside the spinlock during concurrent TLB invalidations. This concurrently executed bug, identified as CWE-1066 and indicated in NVD-CWE-noinfo, can cause completion waits to time out unpredictably, violating wait_on_sem() ordering assumptions and potentially leading to kernel hangs or crashes.

Affected Systems

Any Linux kernel that includes the AMD IOMMU subsystem before the patch commit. The vulnerability is not tied to a specific kernel release; all versions containing the vulnerable code path are potentially impacted. The fix is available in recent kernel releases after commit 48caa7542a795c9679ec1bd1bc2592e05a7369a4.

Risk and Exploitability

The CVSS score is 5.5, EPSS score is < 1%, and it is not listed in CISA KEV. Exploitation would require triggering concurrent TLB invalidations and queuing CMD_COMPL_WAIT commands, a scenario that generally demands privileged or kernel-level code. Consequently, local or remote attackers with kernel execution capabilities could abuse the race to cause a denial of service, but the probability of exploitation remains uncertain. Given the impact of a kernel crash and lack of user‑level mitigations, the risk is considered high for affected systems.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the Linux kernel update that includes commit 48caa7542a795c9679ec1bd1bc2592e05a7369a4 or later.
  • Reboot the system so the updated kernel and IOMMU driver load.
  • Monitor kernel logs (dmesg, /var/log/kern.log) for any IOMMU or TLB invalidation related warnings; if issues persist, consider temporarily disabling AMD IOMMU or applying a newer kernel.

Generated by OpenCVE AI on May 12, 2026 at 21:32 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DSA Debian DSA DSA-6274-1 linux security update
History
Type Values Removed Values Added
Weaknesses NVD-CWE-noinfo
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
Weaknesses CWE-362
Type Values Removed Values Added
Weaknesses CWE-362
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: iommu/amd: serialize sequence allocation under concurrent TLB invalidations With concurrent TLB invalidations, completion wait randomly gets timed out because cmd_sem_val was incremented outside the IOMMU spinlock, allowing CMD_COMPL_WAIT commands to be queued out of sequence and breaking the ordering assumption in wait_on_sem(). Move the cmd_sem_val increment under iommu->lock so completion sequence allocation is serialized with command queuing. And remove the unnecessary return.
Title iommu/amd: serialize sequence allocation under concurrent TLB invalidations
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:25 PM
Reserved
May 1, 2026, 2:12 PM
Status
Modified
Published
May 6, 2026, 12:16 PM
Modified
Nov 11, 2026, 8:10 PM
Severity
Public date
May 6, 2026, 12:00 AM