drm/amdgpu/userq: only accept doorbell BOs as queue doorbell
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.57, 7.2.11
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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)
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
From f09c1e6077abd1bc2ddd2b97e1135215801ca7f9 · fixed in 112dbe2b10d6d088a6c599980dd960dcbfa55ff0; From f09c1e6077abd1bc2ddd2b97e1135215801ca7f9 · fixed in 8640b3f961d743d6dc0458c2b53a3af434690cc1; From f09c1e6077abd1bc2ddd2b97e1135215801ca7f9 · fixed in 7f7c88dbf4d543f6703e53bdeed380e886733167
- Linux Linux
6.16
- KernelLinux
From 6.16.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.11