CVE-2026-68347

Technical Description

In the Linux kernel, the following vulnerability has been resolved:

iommu/amd: Fix IRQ unsafe locking in gdom allocation

Lockdep complains:

[ 259.410489] =====================================================

[ 259.417287] WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected

[ 259.424667] 7.0.0-g51db1d8d2113 #54 Not tainted

[ 259.429718] -----------------------------------------------------

[ 259.436516] qemu-system-x86/10143 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:

[ 259.444670] ff3b2b1c60305170 (&xa->xa_lock#25){+.+.}-{3:3}, at: __domain_flush_pages+0x17c/0x4b0

[ 259.454485]

and this task is already holding:

[ 259.460991] ff3b2b1c98504cc0 (&domain->lock){-.-.}-{3:3}, at: amd_iommu_iotlb_sync+0x25/0x60

[ 259.470408] which would create a new lock dependency:

[ 259.476041] (&domain->lock){-.-.}-{3:3} -> (&xa->xa_lock#25){+.+.}-{3:3}

[ 259.483615]

but this new dependency connects a HARDIRQ-irq-safe lock:

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References