drm/amdgpu: reject mapping a reserved doorbell to a new queue (CVE-2026-68103) | HOL Guard CVE

High · CVSS 7.1CVE-2026-68103

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

Answer in brief

CVE-2026-68103 records a High severity (CVSS 7.1) vulnerability in drm/amdgpu: reject mapping a reserved doorbell to a new queue. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 10, 2026Updated Aug 17, 2026Source checked Sep 24, 2026First seen by HOL Aug 10, 2026Material review Aug 17, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.1
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1050d258c7c56066d2dcaedf8d0ef66364062adc \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a609b6278bf3cde17eeee6620091465521e4b02c \|\| >=0 <7.1.6	1050d258c7c56066d2dcaedf8d0ef66364062adc, a609b6278bf3cde17eeee6620091465521e4b02c, 7.1.6
Linux/Linuxgeneric	>=8949843762631d9d0fc526dfb61a272dca29fc6f <1050d258c7c56066d2dcaedf8d0ef66364062adc \|\| >=8949843762631d9d0fc526dfb61a272dca29fc6f <a609b6278bf3cde17eeee6620091465521e4b02c	1050d258c7c56066d2dcaedf8d0ef66364062adc, a609b6278bf3cde17eeee6620091465521e4b02c
Linux/Linuxgeneric	6.16	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 1050d258c7c56066d2dcaedf8d0ef66364062adc; Linux/Linux to 1050d258c7c56066d2dcaedf8d0ef66364062adc if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 10, 2026

Sources and claim methodology

Upstream source 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)

Quoted source text, attributed separately from HOL analysis.