CVE-2026-68103

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

Published Aug 10, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
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)

Analysis

AI-generated

Technical impact

In the Linux kernel amdgpu driver, user space can create a queue that requests a doorbell buffer object and offset that is already allocated to an existing queue. The driver uses xa_store_irq to record the mapping; a later queue creation with identical parameters can overwrite the earlier mapping. This flaw allows one queue to hijack the doorbell resources of another, leading to misrouted fence interrupts and potentially corrupting kernel state during cleanup. The weakness corresponds to improper authorization and concurrent resource misuse, as reflected by the CWE identifiers present in the advisory.

Affected Systems

All Linux kernel releases that include the amdgpu graphics driver and lack the patch that replaces xa_store_irq with xa_insert_irq. The vulnerability is present in every kernel version prior to that commit; no specific version numbers are listed, so any older kernel is considered affected.

Risk and Exploitability

The CVSS score of 7.1 signals moderate to high severity. The EPSS score of < 1 % indicates a very low probability that exploitation will be observed in the wild, and the vulnerability is not listed in CISA’s KEV catalog. The likely attack vector is local user space, and it requires a user with sufficient privileges to create an amdgpu queue. This inference is stated explicitly because the description does not specify the attack surface. Once local access is achieved, an attacker could overwrite the doorbell mapping, misroute interrupt handling, and potentially corrupt kernel state.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that applies the commit replacing xa_store_irq with xa_insert_irq, which removes the doorbell reuse flaw.
  • If a kernel upgrade cannot be performed immediately, restrict the amdgpu driver’s usage to only trusted users by enforcing appropriate file permissions and capabilities, thus limiting the local privilege context an attacker can obtain.
  • If the amdgpu driver is not required in your environment, disable or remove the driver to eliminate the attack surface.

Generated by OpenCVE AI on October 20, 2026 at 10:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-662
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-285
Type Values Removed Values Added
Weaknesses CWE-367
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Weaknesses CWE-285
Type Values Removed Values Added
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)
Title drm/amdgpu: reject mapping a reserved doorbell to a new queue
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-367

    Time-of-check Time-of-use (TOCTOU) Race Condition

  • CWE-662

    Improper Synchronization

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 19, 2026, 8:58 PM
Reserved
Jul 30, 2026, 9:28 AM
Status
Received
Published
Aug 10, 2026, 1:19 PM
Modified
Oct 19, 2026, 9:17 PM
Severity
Moderate
Public date
Aug 10, 2026, 12:00 AM