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

High 7.1 Published Updated

A race condition in the AMD GPU driver allows overwriting queue mappings, potentially leading to privilege escalation or denial of service.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-68103?

CVE-2026-68103 is a high-severity vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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)

Weakness: CWE-662

Which versions are affected by CVE-2026-68103?

How do I fix CVE-2026-68103?

Apply the vendor's patch.

Is CVE-2026-68103 being exploited?

There is no known exploitation of CVE-2026-68103 in the wild and no public exploit code.

Sources

Also known as BELL-CVE-2026-68103, DEBIAN-CVE-2026-68103, GHSA-wgx5-5x9q-wrw8, UBUNTU-CVE-2026-68103.

Is CVE-2026-68103 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free