CVE-2026-68329

In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Wait for completion instead of returning early in iommu_completion_wait() need_sync is a per-IOMMU flag shared by all domains and devices behind that IOMMU. It is set whenever a command is queued with sync == true and cleared when a completion-wait (CWAIT) command is queued. However, a cleared need_sync only means that a covering CWAIT has been queued, not that all previously queued commands have actually completed in hardware. iommu_completion_wait() read need_sync locklessly and returned early when it was false. This breaks the "block until all previously queued commands have completed" contract in a multi-CPU scenario: CPU2: queue inv-B => need_sync = true CPU1: queue CWAIT(N); need_sync = false; then wait_on_sem(N) CPU2: read need_sync == false => return 0 (no wait!) CPU2 returns without waiting for any sequence number even though its inv-B may not have completed yet (CWAIT(N), queued after inv-B, has not been signaled). CPU2 then proceeds to, for example, free page-table pages while the IOMMU can still walk stale translations, opening a use-after-free window. This is a logical race in the meaning of the flag, not a memory-visibility issue, so barriers alone do not help. Fix it without losing the optimization of avoiding redundant CWAIT commands: take iommu->lock before testing need_sync, and when it is false do not return early but wait for the last allocated sequence number (cmd_sem_val). Since need_sync == false implies no sync command was queued after the last CWAIT, that CWAIT is FIFO-ordered after every not-yet-completed command, so waiting for its sequence number guarantees all prior commands (possibly queued by another CPU) have completed. The common path with pending work is unchanged and no extra hardware command is issued.

• https://git.kernel.org/stable/c/02f8cefa2ad95ea3754f0cfd6fbae7f866202ccb
• https://git.kernel.org/stable/c/1e75a8255f11c81fb07e81e5029cfd75804350a0
• https://git.kernel.org/stable/c/93494bd446396c257fb589f59894577e96e406e2
• https://git.kernel.org/stable/c/ab7faf5a172ebfdc423ebb3eea4d472740de82f9
• https://git.kernel.org/stable/c/d053eb7e09e10cbdca3fca8b35c1017d438091b2

Published

Aug 10, 2026

Last Modified

Aug 10, 2026

Status

Received

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-68323In the Linux kernel, the following vulnerability has been re…
• CVE-2026-68324In the Linux kernel, the following vulnerability has been re…
• CVE-2026-68325In the Linux kernel, the following vulnerability has been re…
• CVE-2026-68326In the Linux kernel, the following vulnerability has been re…
• CVE-2026-68327In the Linux kernel, the following vulnerability has been re…
• CVE-2026-68328In the Linux kernel, the following vulnerability has been re…
• CVE-2026-6833The a+HRD developed by aEnrich has a SQL Injection vulnerabi…7.1
• CVE-2026-68330In the Linux kernel, the following vulnerability has been re…
• CVE-2026-68331In the Linux kernel, the following vulnerability has been re…
• CVE-2026-68332In the Linux kernel, the following vulnerability has been re…
• CVE-2026-68333In the Linux kernel, the following vulnerability has been re…
• CVE-2026-68334In the Linux kernel, the following vulnerability has been re…