CVE-2026-43220
iommu/amd: serialize sequence allocation under concurrent TLB invalidations
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.2, 6.6.140, 6.12.88
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 6.1.191 · fixed in 6.2
- Linux Linux
From 6.6.128 · fixed in 6.6.140; From 6.12.75 · fixed in 6.12.88
- KernelLinux
From 6.6.128 · fixed in 6.6.140; From 6.12.75 · fixed in 6.12.88