CVE-2026-68103
Last modified
CVE-2026-68103 is a vulnerability of currently unknown severity. 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).
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)
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 1050d258c7c56066d2dcaedf8d0ef66364062adc; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < a609b6278bf3cde17eeee6620091465521e4b02c; < 7.1.6 |
| Linux | Linux | All versions |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68103?
How severe is CVE-2026-68103?
How do I fix CVE-2026-68103?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-68098In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68099In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6810The Booking Calendar Contact Form plugin for WordPress is vu…5.3
- CVE-2026-68100In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68101In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68102In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68104In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68105In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68106In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68107In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68108In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68109In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-68103?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
