{
  "cveId": "CVE-2026-68347",
  "url": "https://patchblox.com/security/cve/CVE-2026-68347",
  "summary": "CVE-2026-68347 is fixed in linux on 1 platform by DEBIAN-CVE-2026-68347 (version 7.1.6-1), released August 11, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  iommu/amd: Fix IRQ unsafe locking in gdom alloca...",
  "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 -\u003E 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 (\u0026xa-\u003Exa_lock#25){\u002B.\u002B.}-{3:3}, at: __domain_flush_pages\u002B0x17c/0x4b0   [  259.454485]                  and this task is already holding:   [  259.460991] ff3b2b1c98504cc0 (\u0026domain-\u003Elock){-.-.}-{3:3}, at: amd_iommu_iotlb_sync\u002B0x25/0x60   [  259.470408] which would create a new lock dependency:   [  259.476041]  (\u0026domain-\u003Elock){-.-.}-{3:3} -\u003E (\u0026xa-\u003Exa_lock#25){\u002B.\u002B.}-{3:3}   [  259.483615]                  but this new dependency connects a HARDIRQ-irq-safe lock:   [  259.492447]  (\u0026domain-\u003Elock){-.-.}-{3:3}   [  259.492449]                  ... which became HARDIRQ-irq-safe at:   [  259.503705]   lock_acquire\u002B0xb6/0x2e0   [  259.507790]   _raw_spin_lock_irqsave\u002B0x3e/0x60   [  259.512748]   amd_iommu_flush_iotlb_all\u002B0x20/0x50   [  259.517996]   iommu_dma_free_iova.isra.0\u002B0x1b8/0x1e0   [  259.523534]   __iommu_dma_unmap\u002B0xc2/0x140   [  259.528100]   iommu_dma_unmap_phys\u002B0x55/0xc0   [  259.532863]   dma_unmap_phys\u002B0x274/0x2e0   [  259.537238]   dma_unmap_page_attrs\u002B0x17/0x30   [  259.542000]   nvme_unmap_data\u002B0x13e/0x280   [  259.546473]   nvme_pci_complete_batch\u002B0x45/0x70   [  259.551524]   nvme_irq\u002B0x83/0x90   [  259.555123]   __handle_irq_event_percpu\u002B0x92/0x360   [  259.560466]   handle_irq_event\u002B0x39/0x80   [  259.564841]   handle_edge_irq\u002B0xb2/0x1a0   [  259.569214]   __common_interrupt\u002B0x4e/0x130   [  259.573882]   common_interrupt\u002B0x88/0xa0   [  259.578256]   asm_common_interrupt\u002B0x27/0x40   [  259.583019]   cpuidle_enter_state\u002B0x119/0x5d0   [  259.587877]   cpuidle_enter\u002B0x2e/0x50   [  259.591962]   do_idle\u002B0x153/0x2c0   [  259.595657]   cpu_startup_entry\u002B0x29/0x30   [  259.600128]   start_secondary\u002B0x118/0x150   [  259.604601]   common_startup_64\u002B0x13e/0x141   [  259.609266]                  to a HARDIRQ-irq-unsafe lock:   [  259.615384]  (\u0026xa-\u003Exa_lock#25){\u002B.\u002B.}-{3:3}   [  259.615386]                  ... which became HARDIRQ-irq-unsafe at:   [  259.627039] ...   [  259.627039]   lock_acquire\u002B0xb6/0x2e0   [  259.633071]   _raw_spin_lock\u002B0x2f/0x50   [  259.637250]   amd_iommu_alloc_domain_nested\u002B0x140/0x3c0   [  259.643078]   iommufd_hwpt_alloc\u002B0x272/0x800 [iommufd]   [  259.648813]   iommufd_fops_ioctl\u002B0x14e/0x200 [iommufd]   [  259.654547]   __x64_sys_ioctl\u002B0x9d/0xf0   ...  Since amd_iommu_domain_flush_pages() necessarily holds domain-\u003Elock to do the flush, switch the allocation side in gdom_info_load_or_alloc_locked() to HARDIRQ-safe allocation. The IOMMU_DESTROY-\u003Efree path has the same issue, so switch that path to HARDIRQ-safe locking as well.",
  "published": "2026-08-10T13:20:26Z",
  "severity": "",
  "epss": 0.00162,
  "epssPercentile": 0.05469,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.1.6-1",
      "fix": "DEBIAN-CVE-2026-68347",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-68347",
      "released": "2026-08-11T16:03:09Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-10T07:50:38Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}