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)
Published: 2026-08-10
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

In the Linux amdgpu driver, a user‑space program can request a doorbell buffer object and offset that are already assigned to an existing queue. Because the driver uses xa_store_irq to record the mapping, a subsequent creation of a queue with the same BO and offset can overwrite the previous mapping. This enables a malicious user to route fence interrupts to an incorrect queue and cause cleanup of one queue to erase another’s mapping, potentially corrupting kernel interrupt handling and kernel state. The weakness is an instance of improper authorization and improper use of allowlist mechanisms.

Affected Systems

Linux kernel (amdgpu driver). No specific version information is available; the vulnerability exists in any kernel version prior to the commit that replaces xa_store_irq with xa_insert_irq.

Risk and Exploitability

The CVSS score is 7.1, the EPSS score is < 1%, and the vulnerability is not listed in CISA KEV. Based on the description, it is inferred that an attacker requires local access with kernel or privileged user rights to create a user‑queue and supply the BO and offset. If this is achieved, the attacker can overwrite an existing doorbell mapping, potentially misrouting fence interrupts and corrupting kernel state. The exploitation does not involve network or remote code execution; it requires only local privileged execution.

Generated by OpenCVE AI on August 14, 2026 at 01:51 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that contains the commit replacing xa_store_irq with xa_insert_irq, ensuring the amdgpu driver no longer reuses doorbell mappings.
  • If an immediate kernel update is not possible, configure the system to restrict untrusted users from loading or interacting with the amdgpu driver by enforcing appropriate capabilities and user‑group restrictions, thereby limiting local attacker context.
  • If the amdgpu driver is unnecessary for the system, consider disabling or removing the driver entirely to eliminate the attack surface.

Generated by OpenCVE AI on August 14, 2026 at 01:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 13 Aug 2026 22:45:00 +0000

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'}


Thu, 13 Aug 2026 09:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-285

Wed, 12 Aug 2026 00:15:00 +0000

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


Mon, 10 Aug 2026 20:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-285

Mon, 10 Aug 2026 12:30:00 +0000

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

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T04:58:51.492Z

Reserved: 2026-07-30T09:28:09.368Z

Link: CVE-2026-68103

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-10T13:19:54.983

Modified: 2026-08-17T05:18:09.657

Link: CVE-2026-68103

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-10T00:00:00Z

Links: CVE-2026-68103 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-14T02:00:15Z

Weaknesses
  • CWE-367

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