CVE-2026-68347

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-68347", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-07-30T09:28:09.384Z", "datePublished": "2026-08-10T12:03:24.020Z", "dateUpdated": "2026-08-17T05:03:47.926Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-17T05:03:47.926Z"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd: Fix IRQ unsafe locking in gdom allocation\n\nLockdep complains:\n\n [ 259.410489] =====================================================\n [ 259.417287] WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected\n [ 259.424667] 7.0.0-g51db1d8d2113 #54 Not tainted\n [ 259.429718] -----------------------------------------------------\n [ 259.436516] qemu-system-x86/10143 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:\n [ 259.444670] ff3b2b1c60305170 (&xa->xa_lock#25){+.+.}-{3:3}, at: __domain_flush_pages+0x17c/0x4b0\n [ 259.454485]\n and this task is already holding:\n [ 259.460991] ff3b2b1c98504cc0 (&domain->lock){-.-.}-{3:3}, at: amd_iommu_iotlb_sync+0x25/0x60\n [ 259.470408] which would create a new lock dependency:\n [ 259.476041] (&domain->lock){-.-.}-{3:3} -> (&xa->xa_lock#25){+.+.}-{3:3}\n [ 259.483615]\n but this new dependency connects a HARDIRQ-irq-safe lock:\n [ 259.492447] (&domain->lock){-.-.}-{3:3}\n [ 259.492449]\n ... which became HARDIRQ-irq-safe at:\n [ 259.503705] lock_acquire+0xb6/0x2e0\n [ 259.507790] _raw_spin_lock_irqsave+0x3e/0x60\n [ 259.512748] amd_iommu_flush_iotlb_all+0x20/0x50\n [ 259.517996] iommu_dma_free_iova.isra.0+0x1b8/0x1e0\n [ 259.523534] __iommu_dma_unmap+0xc2/0x140\n [ 259.528100] iommu_dma_unmap_phys+0x55/0xc0\n [ 259.532863] dma_unmap_phys+0x274/0x2e0\n [ 259.537238] dma_unmap_page_attrs+0x17/0x30\n [ 259.542000] nvme_unmap_data+0x13e/0x280\n [ 259.546473] nvme_pci_complete_batch+0x45/0x70\n [ 259.551524] nvme_irq+0x83/0x90\n [ 259.555123] __handle_irq_event_percpu+0x92/0x360\n [ 259.560466] handle_irq_event+0x39/0x80\n [ 259.564841] handle_edge_irq+0xb2/0x1a0\n [ 259.569214] __common_interrupt+0x4e/0x130\n [ 259.573882] common_interrupt+0x88/0xa0\n [ 259.578256] asm_common_interrupt+0x27/0x40\n [ 259.583019] cpuidle_enter_state+0x119/0x5d0\n [ 259.587877] cpuidle_enter+0x2e/0x50\n [ 259.591962] do_idle+0x153/0x2c0\n [ 259.595657] cpu_startup_entry+0x29/0x30\n [ 259.600128] start_secondary+0x118/0x150\n [ 259.604601] common_startup_64+0x13e/0x141\n [ 259.609266]\n to a HARDIRQ-irq-unsafe lock:\n [ 259.615384] (&xa->xa_lock#25){+.+.}-{3:3}\n [ 259.615386]\n ... which became HARDIRQ-irq-unsafe at:\n [ 259.627039] ...\n [ 259.627039] lock_acquire+0xb6/0x2e0\n [ 259.633071] _raw_spin_lock+0x2f/0x50\n [ 259.637250] amd_iommu_alloc_domain_nested+0x140/0x3c0\n [ 259.643078] iommufd_hwpt_alloc+0x272/0x800 [iommufd]\n [ 259.648813] iommufd_fops_ioctl+0x14e/0x200 [iommufd]\n [ 259.654547] __x64_sys_ioctl+0x9d/0xf0\n ...\n\nSince amd_iommu_domain_flush_pages() necessarily holds domain->lock to do the\nflush, switch the allocation side in gdom_info_load_or_alloc_locked() to\nHARDIRQ-safe allocation. The IOMMU_DESTROY->free path has the same issue,\nso switch that path to HARDIRQ-safe locking as well."}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["drivers/iommu/amd/nested.c"], "versions": [{"version": "757d2b1fdf5b7d6eead5963a49b5780617987ab8", "lessThan": "e0c78cdf35af3ada05f9309f4641e9f83c945dbd", "status": "affected", "versionType": "git"}, {"version": "757d2b1fdf5b7d6eead5963a49b5780617987ab8", "lessThan": "0db3a430d9681fdb29890bef6934cd89cd1745d0", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["drivers/iommu/amd/nested.c"], "versions": [{"version": "7.0", "status": "affected"}, {"version": "0", "lessThan": "7.0", "status": "unaffected", "versionType": "semver"}, {"version": "7.1.6", "lessThanOrEqual": "7.1.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.2", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "7.0", "versionEndExcluding": "7.1.6"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "7.0", "versionEndExcluding": "7.2"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/e0c78cdf35af3ada05f9309f4641e9f83c945dbd"}, {"url": "https://git.kernel.org/stable/c/0db3a430d9681fdb29890bef6934cd89cd1745d0"}], "title": "iommu/amd: Fix IRQ unsafe locking in gdom allocation", "x_generator": {"engine": "bippy-1.2.0"}}}}

{}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Linux", "programFiles": ["drivers/iommu/amd/nested.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"lessThan": "e0c78cdf35af3ada05f9309f4641e9f83c945dbd", "status": "affected", "version": "757d2b1fdf5b7d6eead5963a49b5780617987ab8", "versionType": "git"}, {"lessThan": "0db3a430d9681fdb29890bef6934cd89cd1745d0", "status": "affected", "version": "757d2b1fdf5b7d6eead5963a49b5780617987ab8", "versionType": "git"}]}, {"defaultStatus": "affected", "product": "Linux", "programFiles": ["drivers/iommu/amd/nested.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"status": "affected", "version": "7.0"}, {"lessThan": "7.0", "status": "unaffected", "version": "0", "versionType": "semver"}, {"lessThanOrEqual": "7.1.*", "status": "unaffected", "version": "7.1.6", "versionType": "semver"}, {"lessThanOrEqual": "*", "status": "unaffected", "version": "7.2", "versionType": "original_commit_for_fix"}]}], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd: Fix IRQ unsafe locking in gdom allocation\n\nLockdep complains:\n\n [ 259.410489] =====================================================\n [ 259.417287] WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected\n [ 259.424667] 7.0.0-g51db1d8d2113 #54 Not tainted\n [ 259.429718] -----------------------------------------------------\n [ 259.436516] qemu-system-x86/10143 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:\n [ 259.444670] ff3b2b1c60305170 (&xa->xa_lock#25){+.+.}-{3:3}, at: __domain_flush_pages+0x17c/0x4b0\n [ 259.454485]\n and this task is already holding:\n [ 259.460991] ff3b2b1c98504cc0 (&domain->lock){-.-.}-{3:3}, at: amd_iommu_iotlb_sync+0x25/0x60\n [ 259.470408] which would create a new lock dependency:\n [ 259.476041] (&domain->lock){-.-.}-{3:3} -> (&xa->xa_lock#25){+.+.}-{3:3}\n [ 259.483615]\n but this new dependency connects a HARDIRQ-irq-safe lock:\n [ 259.492447] (&domain->lock){-.-.}-{3:3}\n [ 259.492449]\n ... which became HARDIRQ-irq-safe at:\n [ 259.503705] lock_acquire+0xb6/0x2e0\n [ 259.507790] _raw_spin_lock_irqsave+0x3e/0x60\n [ 259.512748] amd_iommu_flush_iotlb_all+0x20/0x50\n [ 259.517996] iommu_dma_free_iova.isra.0+0x1b8/0x1e0\n [ 259.523534] __iommu_dma_unmap+0xc2/0x140\n [ 259.528100] iommu_dma_unmap_phys+0x55/0xc0\n [ 259.532863] dma_unmap_phys+0x274/0x2e0\n [ 259.537238] dma_unmap_page_attrs+0x17/0x30\n [ 259.542000] nvme_unmap_data+0x13e/0x280\n [ 259.546473] nvme_pci_complete_batch+0x45/0x70\n [ 259.551524] nvme_irq+0x83/0x90\n [ 259.555123] __handle_irq_event_percpu+0x92/0x360\n [ 259.560466] handle_irq_event+0x39/0x80\n [ 259.564841] handle_edge_irq+0xb2/0x1a0\n [ 259.569214] __common_interrupt+0x4e/0x130\n [ 259.573882] common_interrupt+0x88/0xa0\n [ 259.578256] asm_common_interrupt+0x27/0x40\n [ 259.583019] cpuidle_enter_state+0x119/0x5d0\n [ 259.587877] cpuidle_enter+0x2e/0x50\n [ 259.591962] do_idle+0x153/0x2c0\n [ 259.595657] cpu_startup_entry+0x29/0x30\n [ 259.600128] start_secondary+0x118/0x150\n [ 259.604601] common_startup_64+0x13e/0x141\n [ 259.609266]\n to a HARDIRQ-irq-unsafe lock:\n [ 259.615384] (&xa->xa_lock#25){+.+.}-{3:3}\n [ 259.615386]\n ... which became HARDIRQ-irq-unsafe at:\n [ 259.627039] ...\n [ 259.627039] lock_acquire+0xb6/0x2e0\n [ 259.633071] _raw_spin_lock+0x2f/0x50\n [ 259.637250] amd_iommu_alloc_domain_nested+0x140/0x3c0\n [ 259.643078] iommufd_hwpt_alloc+0x272/0x800 [iommufd]\n [ 259.648813] iommufd_fops_ioctl+0x14e/0x200 [iommufd]\n [ 259.654547] __x64_sys_ioctl+0x9d/0xf0\n ...\n\nSince amd_iommu_domain_flush_pages() necessarily holds domain->lock to do the\nflush, switch the allocation side in gdom_info_load_or_alloc_locked() to\nHARDIRQ-safe allocation. The IOMMU_DESTROY->free path has the same issue,\nso switch that path to HARDIRQ-safe locking as well."}], "id": "CVE-2026-68347", "lastModified": "2026-08-17T06:17:42.917", "metrics": {}, "published": "2026-08-10T13:20:26.553", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/0db3a430d9681fdb29890bef6934cd89cd1745d0"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/e0c78cdf35af3ada05f9309f4641e9f83c945dbd"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Received"}

{"bugzilla": {"description": "kernel: Linux kernel: AMD IOMMU unsafe locking leads to denial of service", "id": "2513262", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2513262"}, "csaw": false, "cvss3": {"cvss3_base_score": "4.7", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H", "status": "draft"}, "cwe": "CWE-833", "details": ["In the Linux kernel, the following vulnerability has been resolved:\niommu/amd: Fix IRQ unsafe locking in gdom allocation\nLockdep complains:\n[ 259.410489] =====================================================\n[ 259.417287] WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected\n[ 259.424667] 7.0.0-g51db1d8d2113 #54 Not tainted\n[ 259.429718] -----------------------------------------------------\n[ 259.436516] qemu-system-x86/10143 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:\n[ 259.444670] ff3b2b1c60305170 (&xa->xa_lock#25){+.+.}-{3:3}, at: __domain_flush_pages+0x17c/0x4b0\n[ 259.454485]\nand this task is already holding:\n[ 259.460991] ff3b2b1c98504cc0 (&domain->lock){-.-.}-{3:3}, at: amd_iommu_iotlb_sync+0x25/0x60\n[ 259.470408] which would create a new lock dependency:\n[ 259.476041] (&domain->lock){-.-.}-{3:3} -> (&xa->xa_lock#25){+.+.}-{3:3}\n[ 259.483615]\nbut this new dependency connects a HARDIRQ-irq-safe lock:\n[ 259.492447] (&domain->lock){-.-.}-{3:3}\n[ 259.492449]\n... which became HARDIRQ-irq-safe at:\n[ 259.503705] lock_acquire+0xb6/0x2e0\n[ 259.507790] _raw_spin_lock_irqsave+0x3e/0x60\n[ 259.512748] amd_iommu_flush_iotlb_all+0x20/0x50\n[ 259.517996] iommu_dma_free_iova.isra.0+0x1b8/0x1e0\n[ 259.523534] __iommu_dma_unmap+0xc2/0x140\n[ 259.528100] iommu_dma_unmap_phys+0x55/0xc0\n[ 259.532863] dma_unmap_phys+0x274/0x2e0\n[ 259.537238] dma_unmap_page_attrs+0x17/0x30\n[ 259.542000] nvme_unmap_data+0x13e/0x280\n[ 259.546473] nvme_pci_complete_batch+0x45/0x70\n[ 259.551524] nvme_irq+0x83/0x90\n[ 259.555123] __handle_irq_event_percpu+0x92/0x360\n[ 259.560466] handle_irq_event+0x39/0x80\n[ 259.564841] handle_edge_irq+0xb2/0x1a0\n[ 259.569214] __common_interrupt+0x4e/0x130\n[ 259.573882] common_interrupt+0x88/0xa0\n[ 259.578256] asm_common_interrupt+0x27/0x40\n[ 259.583019] cpuidle_enter_state+0x119/0x5d0\n[ 259.587877] cpuidle_enter+0x2e/0x50\n[ 259.591962] do_idle+0x153/0x2c0\n[ 259.595657] cpu_startup_entry+0x29/0x30\n[ 259.600128] start_secondary+0x118/0x150\n[ 259.604601] common_startup_64+0x13e/0x141\n[ 259.609266]\nto a HARDIRQ-irq-unsafe lock:\n[ 259.615384] (&xa->xa_lock#25){+.+.}-{3:3}\n[ 259.615386]\n... which became HARDIRQ-irq-unsafe at:\n[ 259.627039] ...\n[ 259.627039] lock_acquire+0xb6/0x2e0\n[ 259.633071] _raw_spin_lock+0x2f/0x50\n[ 259.637250] amd_iommu_alloc_domain_nested+0x140/0x3c0\n[ 259.643078] iommufd_hwpt_alloc+0x272/0x800 [iommufd]\n[ 259.648813] iommufd_fops_ioctl+0x14e/0x200 [iommufd]\n[ 259.654547] __x64_sys_ioctl+0x9d/0xf0\n...\nSince amd_iommu_domain_flush_pages() necessarily holds domain->lock to do the\nflush, switch the allocation side in gdom_info_load_or_alloc_locked() to\nHARDIRQ-safe allocation. The IOMMU_DESTROY->free path has the same issue,\nso switch that path to HARDIRQ-safe locking as well.", "A flaw was found in the Linux kernel's AMD IOMMU (Input/Output Memory Management Unit) driver. This vulnerability is caused by an unsafe lock order during the allocation of graphics domains (gdom) and within the IOMMU_DESTROY free path. This issue could lead to a system crash or a denial of service (DoS) due to a kernel concurrency problem."], "name": "CVE-2026-68347", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:10", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 10"}, {"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/a:redhat:enterprise_linux_nvidia:", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux for NVIDIA 26"}, {"cpe": "cpe:/a:redhat:openshift:4", "fix_state": "Not affected", "package_name": "rhcos", "product_name": "Red Hat OpenShift Container Platform 4"}], "public_date": "2026-08-10T12:03:24Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-68347\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-68347\nhttps://git.kernel.org/stable/c/0db3a430d9681fdb29890bef6934cd89cd1745d0\nhttps://git.kernel.org/stable/c/e0c78cdf35af3ada05f9309f4641e9f83c945dbd"], "threat_severity": "Moderate"}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[757d2b1fdf5b7d6eead5963a49b5780617987ab8,e0c78cdf35af3ada05f9309f4641e9f83c945dbd)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "code_commit", "value": "[757d2b1fdf5b7d6eead5963a49b5780617987ab8,0db3a430d9681fdb29890bef6934cd89cd1745d0)"}}], "enrichment": {"confidence": 99.0, "confidence_source": "inferred", "scores": [{"score": 99.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "Linux", "source": "cna", "vendor": "Linux"}, "product": "linux_kernel", "vendor": "linux"}, {"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "7.0"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "generic", "value": "[0,7.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "semver", "value": "[7.1.6,8.0.0)"}}, {"platform": null, "status": "unaffected", "versions": {"scheme": "generic", "value": "[7.2-rc5,*]"}}], "enrichment": {"confidence": 99.0, "confidence_source": "inferred", "scores": [{"score": 99.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "Linux", "source": "cna", "vendor": "Linux"}, "product": "linux_kernel", "vendor": "linux"}], "created": "2026-08-10T17:30:17.999031+00:00", "updated": "2026-08-13T04:00:09.654800+00:00", "vendors": ["linux", "linux$PRODUCT$linux_kernel"]}