drm/amdgpu/userq: fix access to stale wptr mapping
- 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.0.9
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: fix access to stale wptr mapping Use drm_exec to take both locks i.e vm root bo and wptr_obj bo to access the mapping data properly. This fixes the security issue of unmap the wptr_obj while a queue creation is in progress and passing other bo at same address. (cherry picked from commit 1fc6c8ab45dbee096469c08c13f6099d57a52d6c)
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 5fb2f7fc21a3668e5794cc0d153641b9719713e1 · fixed in 2da62dbb4169e758c0b1a9378b39a373bf4fb111; From 5fb2f7fc21a3668e5794cc0d153641b9719713e1 · fixed in 336a9186f3a4b65bbd865d93936605ac8a1a3991; From 5fb2f7fc21a3668e5794cc0d153641b9719713e1 · fixed in 6da7b1242da4455b11c24ce667d1cab1a348c8ea
- Linux Linux
6.16
- KernelLinux
From 6.16.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.0.9