CVE-2026-68347

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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: [ 259.492447] (&domain->lock){-.-.}-{3:3} [ 259.492449] ... which became HARDIRQ-irq-safe at: [ 259.503705] lock_acquire+0xb6/0x2e0 [ 259.507790] _raw_spin_lock_irqsave+0x3e/0x60 [ 259.512748] amd_iommu_flush_iotlb_all+0x20/0x50 [ 259.517996] iommu_dma_free_iova.isra.0+0x1b8/0x1e0 [ 259.523534] __iommu_dma_unmap+0xc2/0x140 [ 259.528100] iommu_dma_unmap_phys+0x55/0xc0 [ 259.532863] dma_unmap_phys+0x274/0x2e0 [ 259.537238] dma_unmap_page_attrs+0x17/0x30 [ 259.542000] nvme_unmap_data+0x13e/0x280 [ 259.546473] nvme_pci_complete_batch+0x45/0x70 [ 259.551524] nvme_irq+0x83/0x90 [ 259.555123] __handle_irq_event_percpu+0x92/0x360 [ 259.560466] handle_irq_event+0x39/0x80 [ 259.564841] handle_edge_irq+0xb2/0x1a0 [ 259.569214] __common_interrupt+0x4e/0x130 [ 259.573882] common_interrupt+0x88/0xa0 [ 259.578256] asm_common_interrupt+0x27/0x40 [ 259.583019] cpuidle_enter_state+0x119/0x5d0 [ 259.587877] cpuidle_enter+0x2e/0x50 [ 259.591962] do_idle+0x153/0x2c0 [ 259.595657] cpu_startup_entry+0x29/0x30 [ 259.600128] start_secondary+0x118/0x150 [ 259.604601] common_startup_64+0x13e/0x141 [ 259.609266] to a HARDIRQ-irq-unsafe lock: [ 259.615384] (&xa->xa_lock#25){+.+.}-{3:3} [ 259.615386] ... which became HARDIRQ-irq-unsafe at: [ 259.627039] ... [ 259.627039] lock_acquire+0xb6/0x2e0 [ 259.633071] _raw_spin_lock+0x2f/0x50 [ 259.637250] amd_iommu_alloc_domain_nested+0x140/0x3c0 [ 259.643078] iommufd_hwpt_alloc+0x272/0x800 [iommufd] [ 259.648813] iommufd_fops_ioctl+0x14e/0x200 [iommufd] [ 259.654547] __x64_sys_ioctl+0x9d/0xf0 ...

Since amd_iommu_domain_flush_pages() necessarily holds domain->lock to do the flush, switch the allocation side in gdom_info_load_or_alloc_locked() to HARDIRQ-safe allocation. The IOMMU_DESTROY->free path has the same issue, so switch that path to HARDIRQ-safe locking as well.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 10, 2026

Last Modified

August 17, 2026

References (2)

Vendor Advisories for CVE-2026-68347(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (161 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Data Freshness Timeline

(refreshed 8× in last 7d / 36× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 86 is merged into the row it repeats.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-18 03:19 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-10-12 15:45 UTCEG score recompute
  11. 2026-10-11 19:30 UTCEG score recompute
  12. 2026-10-11 16:45 UTCEG score recompute
  13. 2026-10-11 14:06 UTCEG score recompute
  14. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-04 05:22 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
Show 60 more
  1. 2026-09-30 22:38 UTCEG score recompute
  2. 2026-09-30 22:38 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  3. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-09-27 13:06 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  7. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-09-23 02:53 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  10. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-09-20 01:50 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  13. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-09-17 00:47 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  15. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-09-13 19:56 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  18. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-09-10 18:53 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  21. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-09-07 17:49 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  23. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  26. 2026-09-04 16:46 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  27. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  28. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  29. 2026-09-01 15:24 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  30. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  31. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  32. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  33. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  34. 2026-08-29 11:08 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  35. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  36. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  37. 2026-08-26 09:59 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  38. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  39. 2026-08-23 08:43 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  40. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  42. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  43. 2026-08-20 07:35 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  44. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  46. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  47. 2026-08-17 06:32 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  48. 2026-08-17 06:18 UTCNVD update
  49. 2026-08-17 05:36 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  50. 2026-08-17 05:25 UTCMITRE cvelistV5
  51. 2026-08-16 15:31 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  52. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  53. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  54. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  55. 2026-08-13 14:28 UTCEG score recompute
  56. 2026-08-13 14:28 UTCGHSA enrichmentGHSA-q9gw-ch4p-mf89
  57. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  58. 2026-08-10 13:24 UTCNVD update
  59. 2026-08-10 12:18 UTCEG score recompute
  60. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-68347?
CVE-2026-68347 is a vulnerability whose severity is not yet rated; its CVE record was published on August 10, 2026. 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]…
When was the CVE record for CVE-2026-68347 published?
The CVE record for CVE-2026-68347 was published on August 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 17, 2026; the record at its source may have been updated since.
Is CVE-2026-68347 actively exploited?
CVE-2026-68347 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-68347?
A fix for CVE-2026-68347 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68347 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68347

Explore →

Is Your Infrastructure Affected by CVE-2026-68347?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs