drm/amdgpu: reject mapping a reserved doorbell to a new queue
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1050d258c7c56066d2dcaedf8d0ef66364062adc, Kernel a609b6278bf3cde17eeee6620091465521e4b02c and Kernel 7.1.6.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.16, >=8949843762631d9d0fc526dfb61a272dca29fc6f <1050d258c7c56066d2dcaedf8d0ef66364062adc, >=8949843762631d9d0fc526dfb61a272dca29fc6f <a609b6278bf3cde17eeee6620091465521e4b02c | 1050d258c7c56066d2dcaedf8d0ef66364062adc, a609b6278bf3cde17eeee6620091465521e4b02c |
| linux-kernel: Kernel | >=6.16.0 <7.1.6 | 7.1.6 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket