Linux Kernel up to 5.17.2 drm/amd/amdgpu/amdgpu_cs amdgpu_cs_fence_to_handle_ioctl reference count

Summaryinfo

A vulnerability was found in Linux Kernel up to 5.17.2. It has been rated as critical. This vulnerability affects the function amdgpu_cs_fence_to_handle_ioctl of the file drm/amd/amdgpu/amdgpu_cs. Performing a manipulation results in reference count. This vulnerability is known as CVE-2022-49137. No exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Linux Kernel up to 5.17.2. It has been classified as critical. This affects the function amdgpu_cs_fence_to_handle_ioctl of the file drm/amd/amdgpu/amdgpu_cs. The manipulation with an unknown input leads to a reference count vulnerability. CWE is classifying the issue as CWE-911. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count. This is going to have an impact on availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-49137 since 02/26/2025. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 237099 (SUSE SLES12 Security Update : kernel (SUSE-SU-2025:01600-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.19.238, 5.4.189, 5.10.111, 5.15.34, 5.16.20 or 5.17.3 eliminates this vulnerability. Applying the patch 72d77ddb2224ebc00648f4f78f8a9a259dccbdf7/4009f104b02b223d1a11d74b36b1cc083bc37028/927beb05aaa429c883cc0ec6adc48964b187e291/3edd8646cb7c11b57c90e026bda6f21076223f5b/b6d1f7d97c81ebaf2cda9c4c943ee2e484fffdcf/bc2d5c0775c839e2b072884f4ee6a93ba410f107/dfced44f122c500004a48ecc8db516bb6a295a1b is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (237099). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 4.19.237
• 5.4.188
• 5.10.110
• 5.15.0
• 5.15.1
• 5.15.2
• 5.15.3
• 5.15.4
• 5.15.5
• 5.15.6
• 5.15.7
• 5.15.8
• 5.15.9
• 5.15.10
• 5.15.11
• 5.15.12
• 5.15.13
• 5.15.14
• 5.15.15
• 5.15.16
• 5.15.17
• 5.15.18
• 5.15.19
• 5.15.20
• 5.15.21
• 5.15.22
• 5.15.23
• 5.15.24
• 5.15.25
• 5.15.26
• 5.15.27
• 5.15.28
• 5.15.29
• 5.15.30
• 5.15.31
• 5.15.32
• 5.15.33
• 5.16.0
• 5.16.1
• 5.16.2
• 5.16.3
• 5.16.4
• 5.16.5
• 5.16.6
• 5.16.7
• 5.16.8
• 5.16.9
• 5.16.10
• 5.16.11
• 5.16.12
• 5.16.13
• 5.16.14
• 5.16.15
• 5.16.16
• 5.16.17
• 5.16.18
• 5.16.19
• 5.17.0
• 5.17.1
• 5.17.2

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion