drm/amdgpu: change vm->task_info handling
- 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.6.160
- 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: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: change vm->task_info handling This patch changes the handling and lifecycle of vm->task_info object. The major changes are: • vm->task_info is a dynamically allocated ptr now, and its uasge is reference counted. • introducing two new helper funcs for task_info lifecycle management • amdgpu_vm_get_task_info: reference counts up task_info before returning this info • amdgpu_vm_put_task_info: reference counts down task_info • last put to task_info() frees task_info from the vm. This patch also does logistical changes required for existing usage of vm->task_info. V2: Do not block all the prints when task_info not found (Felix) V3: Fixed review comments from Felix • Fix wrong indentation • No debug message for -ENOMEM • Add NULL check for task_info • Do not duplicate the debug messages (ti vs no ti) • Get first reference of task_info in vm_init(), put last in vm_fini() V4: Fixed review comments from Felix • fix double reference increment in create_task_info • change amdgpu_vm_get_task_info_pasid • additional changes in amdgpu_gem.c while porting
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From d38ceaf99ed015f2a0b9af3499791bd3a3daae21 · fixed in 251840f22eff35c25de531a3fcb523df94c128c0; From d38ceaf99ed015f2a0b9af3499791bd3a3daae21 · fixed in b8f67b9ddf4f8fe6dd536590712b5912ad78f99c
- Linux Linux
4.2
- KernelLinux
From 4.2.0 · fixed in 6.6.160