Advisory

DEBIAN-CVE-2026-68329

Also known as: CVE-2026-68329

Summary

The record has no summary.

Details

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.

Severity

High Basis: CVSS v3 score 8.8, vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Dates

Published
2026-08-10 13:20 UTC
Modified
2026-11-15 18:01 UTC

Affected packages and fixes

linux

Debian packages (deb) · Debian 12

Affected

  • introduced 0, fixed 6.1.192-1 (ecosystem)

Fixed versions

6.1.192-1

Fix

  • Fixed version 6.1.192-1
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

linux

Debian packages (deb) · Debian 13

Affected

  • introduced 0, fixed 6.12.101-1 (ecosystem)

Fixed versions

6.12.101-1

Fix

  • Fixed version 6.12.101-1
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

linux

Debian packages (deb) · Debian 14

Affected

  • introduced 0, fixed 7.1.6-1 (ecosystem)

Fixed versions

7.1.6-1

Fix

  • Fixed version 7.1.6-1
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

linux-6.12

Debian packages (deb) · Debian 12

Affected

  • introduced 0, fixed 6.12.101-1~deb12u1 (ecosystem)

Fixed versions

6.12.101-1~deb12u1

Fix

  • Fixed version 6.12.101-1~deb12u1
    sudo apt-get update && sudo apt-get upgrade

This command upgrades the distribution's packages. Compare the fixed version with the version you have installed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: Debian Security Tracker (converted by OSV.dev)

Debian Security Tracker, converted to OSV by OSV.dev.

Sources & licences