# CVE-2026-68103: drm/amdgpu: reject mapping a reserved doorbell to a new queue

CVE-2026-68103 is fixed in linux on 1 platform by DEBIAN-CVE-2026-68103 (version 7.1.6-1), released August 11, 2026. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2026-68103
- Priority: High
- CVSS: 7.1 (Moderate)
- EPSS: 0.0015
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Aug 10, 2026
- Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-68103

## Description

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)

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 14 | 7.1.6-1 | [DEBIAN-CVE-2026-68103](https://patchblox.com/security/data/fix/linux/debian-cve-2026-68103.md) | Aug 11, 2026 |

---

Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.