drm/amdgpu/userq: only accept doorbell BOs as queue doorbell
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 112dbe2b10d6d088a6c599980dd960dcbfa55ff0, Kernel 7f7c88dbf4d543f6703e53bdeed380e886733167, Kernel 8640b3f961d743d6dc0458c2b53a3af434690cc1 and 2 more.
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: only accept doorbell BOs as queue doorbell amdgpu_userq_get_doorbell_index() pins any BO passed as doorbell_handle into the doorbell domain. For a regular BO, TTM moves it with ttm_bo_move_null() and its contents are lost. Since an importer on the same device gets the exporter's GEM object, a client can do this to a buffer another client shared with it. Reject BOs that were not created in the doorbell domain. v2: drop the error message, use a local abo variable (Christian) (cherry picked from commit f7497bbc19db4821c62b9d97b31c9086feb2d917)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.16, >=f09c1e6077abd1bc2ddd2b97e1135215801ca7f9 <112dbe2b10d6d088a6c599980dd960dcbfa55ff0, >=f09c1e6077abd1bc2ddd2b97e1135215801ca7f9 <7f7c88dbf4d543f6703e53bdeed380e886733167, >=f09c1e6077abd1bc2ddd2b97e1135215801ca7f9 <8640b3f961d743d6dc0458c2b53a3af434690cc1 | 112dbe2b10d6d088a6c599980dd960dcbfa55ff0, 7f7c88dbf4d543f6703e53bdeed380e886733167, 8640b3f961d743d6dc0458c2b53a3af434690cc1 |
| linux-kernel: Kernel | >=6.16.0 <6.18.57, >=6.19.0 <7.2.11 | 6.18.57, 7.2.11 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket