CVE-2026-68103

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

drm/amdgpu: reject mapping a reserved doorbell to a new queue

When creating an user-queue, the user space provides a doorbell BO handle and an offset within the bo to obtain a doorbell.

However current implementation using xa_store_irq() to store a doorbell, which allows a later queue created with the same BO and offset parameters to overwrite an existing queue and doorbell mapping.

This can cause problems like misrouting fence IRQ processing to a wrong queue, and mislead the cleanup process of one queue erasing the mapping of another queue.

This commit fixes this issue by replacing xa_store_irq with xa_insert_irq, which rejects mapping a reserved doorbell to a newly created queue

(cherry picked from commit 6244eae22966350db52faf9c1369d3b2ffc5de4e)

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
36(Track)
EG Risk 36/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

drm/amdgpu: reject mapping a reserved doorbell to a new queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a609b6278bf3cde17eeee6620091465521e4b02c
generic

drm/amdgpu: reject mapping a reserved doorbell to a new queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1050d258c7c56066d2dcaedf8d0ef66364062adc

Vendor Advisories for CVE-2026-68103(2)

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

Data Freshness Timeline

(refreshed 30× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 19:33 UTCGHSA enrichment
  3. 2026-08-20 07:32 UTCGHSA enrichment
  4. 2026-08-19 19:31 UTCEG score recompute
  5. 2026-08-19 19:31 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 07:30 UTCGHSA enrichment
  8. 2026-08-18 19:26 UTCEG score recompute
  9. 2026-08-18 19:26 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 07:23 UTCGHSA enrichment
  12. 2026-08-17 19:22 UTCEG score recompute
  13. 2026-08-17 19:22 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 05:41 UTCEG score recompute
  16. 2026-08-17 05:41 UTCGHSA enrichment
  17. 2026-08-17 05:12 UTCEG score recompute
  18. 2026-08-17 05:12 UTCGHSA enrichment
  19. 2026-08-16 23:37 UTCEG score recompute
  20. 2026-08-16 23:37 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 11:35 UTCEG score recompute
  23. 2026-08-16 11:35 UTCGHSA enrichment
  24. 2026-08-15 23:35 UTCGHSA enrichment
  25. 2026-08-15 11:34 UTCEG score recompute
Show 20 more
  1. 2026-08-15 11:34 UTCGHSA enrichment
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 23:33 UTCGHSA enrichment
  4. 2026-08-14 11:32 UTCEG score recompute
  5. 2026-08-14 11:32 UTCGHSA enrichment
  6. 2026-08-13 23:31 UTCEG score recompute
  7. 2026-08-13 23:31 UTCGHSA enrichment
  8. 2026-08-13 22:46 UTCEG score recompute▲ 7.10
  9. 2026-08-13 22:46 UTCGHSA enrichment
  10. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-13 00:22 UTCGHSA enrichment
  13. 2026-08-13 00:22 UTCNVD update
  14. 2026-08-13 00:06 UTCEG score recompute
  15. 2026-08-13 00:06 UTCGHSA enrichment
  16. 2026-08-13 00:05 UTCMITRE cvelistV5
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-10 13:24 UTCNVD update
  19. 2026-08-10 12:22 UTCEG score recompute
  20. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68103?
CVE-2026-68103 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: reject mapping a reserved doorbell to a new queue When creating an user-queue, the user space provides a doorbell BO handle and an offset within the bo to obtain a doorbell. However current implementation using…
When was CVE-2026-68103 disclosed?
CVE-2026-68103 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68103 actively exploited?
CVE-2026-68103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.5% of all scored CVEs.
What is the CVSS score of CVE-2026-68103?
CVE-2026-68103 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-68103?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68103, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68103

Explore →

Is Your Infrastructure Affected by CVE-2026-68103?

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

Start Free Scan →Browse All CVEs