Executive Summary

Informations
Name CVE-2022-49137 First vendor Publication 2025-02-26
Vendor Cve Last vendor Modification 2025-03-13

Security-Database Scoring CVSS v3

Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Overall CVSS Score 5.5
Base Score 5.5 Environmental Score 5.5
impact SubScore 3.6 Temporal Score 5.5
Exploitabality Sub Score 1.8
 
Attack Vector Local Attack Complexity Low
Privileges Required Low User Interaction None
Scope Unchanged Confidentiality Impact None
Integrity Impact None Availability Impact High
Calculate full CVSS 3.0 Vectors scores

Security-Database Scoring CVSS v2

Cvss vector :
Cvss Base Score N/A Attack Range N/A
Cvss Impact Score N/A Attack Complexity N/A
Cvss Expoit Score N/A Authentication N/A
Calculate full CVSS 2.0 Vectors scores

Detail

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.

Original Source

Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-49137

CPE : Common Platform Enumeration

TypeDescriptionCount
Application 7
Os 3528

Sources (Detail)

https://git.kernel.org/stable/c/3edd8646cb7c11b57c90e026bda6f21076223f5b
https://git.kernel.org/stable/c/4009f104b02b223d1a11d74b36b1cc083bc37028
https://git.kernel.org/stable/c/72d77ddb2224ebc00648f4f78f8a9a259dccbdf7
https://git.kernel.org/stable/c/927beb05aaa429c883cc0ec6adc48964b187e291
https://git.kernel.org/stable/c/b6d1f7d97c81ebaf2cda9c4c943ee2e484fffdcf
https://git.kernel.org/stable/c/bc2d5c0775c839e2b072884f4ee6a93ba410f107
https://git.kernel.org/stable/c/dfced44f122c500004a48ecc8db516bb6a295a1b
Source Url

Alert History

If you want to see full details history, please login or register.
0
1
2
3
4
5
6
7
8
9
10
Date Informations
2025-06-26 02:09:17
  • Multiple Updates
2025-06-25 12:22:08
  • Multiple Updates
2025-06-24 02:13:53
  • Multiple Updates
2025-05-27 02:09:28
  • Multiple Updates
2025-03-29 03:14:17
  • Multiple Updates
2025-03-28 13:34:41
  • Multiple Updates
2025-03-28 02:56:46
  • Multiple Updates
2025-03-19 00:21:26
  • Multiple Updates
2025-03-18 00:21:15
  • Multiple Updates
2025-03-14 00:21:43
  • Multiple Updates
2025-02-26 17:20:33
  • First insertion