CVE-2026-68103
MEDIUMDescription
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)
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 4% of all known CVEs.
References
Related Vulnerabilities
Other CWE-662 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-7457 | High | 8.1 | 33% | - | - |
| CVE-2020-14059 | Medium | 6.5 | 4.4% | - | Fix |
| CVE-2018-15555 | Critical | 9.8 | 3.0% | - | - |
| CVE-2016-8368 | High | 8.6 | 2.6% | - | - |
| CVE-2019-17185 | High | 7.5 | 2.2% | - | Fix |
| CVE-2020-3471 | Medium | 6.5 | 1.8% | - | Fix |
Common questions
How do I fix CVE-2026-68103?
Upgrade linux on debian unstable to 7.1.6-1 or later.
Is CVE-2026-68103 being actively exploited?
Not that we know of. CVE-2026-68103 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.15% is the estimated probability that it will be exploited in the next 30 days. That is higher than 4% of all scored CVEs.
How severe is CVE-2026-68103?
CVE-2026-68103 has a CVSS v3 base score of 4.4, rated moderate. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-68103 affect?
Published advisories record a fix for linux (Debian). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-68103
Markdown
[](https://tridentstack.com/cve/CVE-2026-68103)HTML
<a href="https://tridentstack.com/cve/CVE-2026-68103"><img src="https://tridentstack.com/cve/badge/CVE-2026-68103.svg" alt="CVE-2026-68103"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-19.