CVE-2022-49137
drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj
- 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
- 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
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj This issue takes place in an error path in amdgpu_cs_fence_to_handle_ioctl(). When `info->in.what` falls into default case, the function simply returns -EINVAL, forgetting to decrement the reference count of a dma_fence obj, which is bumped earlier by amdgpu_cs_get_fence(). This may result in reference count leaks. Fix it by decreasing the refcount of specific object before returning the error code.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.15
References 7
git.kernel.org
- stable/c/72d77ddb2224ebc00648f4f78f8a9a259dccbdf7
- stable/c/4009f104b02b223d1a11d74b36b1cc083bc37028
- stable/c/927beb05aaa429c883cc0ec6adc48964b187e291
- stable/c/3edd8646cb7c11b57c90e026bda6f21076223f5b
- stable/c/b6d1f7d97c81ebaf2cda9c4c943ee2e484fffdcf
- stable/c/bc2d5c0775c839e2b072884f4ee6a93ba410f107
- stable/c/dfced44f122c500004a48ecc8db516bb6a295a1b