CVE-2022-49137

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-03-14. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

February 26, 2025

Last Modified

August 13, 2026

Advisory Details (7)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dfced44f122c500004a48ecc8db516bb6a295a1b
generic

drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bc2d5c0775c839e2b072884f4ee6a93ba410f107
generic

drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b6d1f7d97c81ebaf2cda9c4c943ee2e484fffdcf
generic

drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3edd8646cb7c11b57c90e026bda6f21076223f5b
generic

drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/927beb05aaa429c883cc0ec6adc48964b187e291
generic

drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4009f104b02b223d1a11d74b36b1cc083bc37028
generic

drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72d77ddb2224ebc00648f4f78f8a9a259dccbdf7

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 4.19.238osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (11 versions)5.10.113-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux5.17.3-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux5.17.3-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux5.17.3-1

Data Freshness Timeline

(refreshed 4× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 154 total refreshes for this CVE.

  1. 2026-09-20 20:13 UTCEPSS rescore
  2. 2026-09-17 12:20 UTCOSV refresh
  3. 2026-09-16 14:05 UTCEPSS rescore
  4. 2026-09-16 05:11 UTCEPSS rescore
  5. 2026-09-15 03:07 UTCEPSS rescore
  6. 2026-09-13 16:44 UTCEPSS rescore
  7. 2026-09-11 14:50 UTCEPSS rescore
  8. 2026-09-11 09:34 UTCEPSS rescore
  9. 2026-09-08 21:57 UTCEPSS rescore
  10. 2026-09-07 15:59 UTCEPSS rescore
  11. 2026-09-06 13:45 UTCEPSS rescore
  12. 2026-09-05 15:25 UTCEPSS rescore
  13. 2026-09-04 13:57 UTCEPSS rescore
  14. 2026-09-04 05:04 UTCEPSS rescore
  15. 2026-09-02 14:09 UTCEPSS rescore
  16. 2026-09-01 13:51 UTCEPSS rescore
  17. 2026-08-30 19:15 UTCEPSS rescore
  18. 2026-08-30 01:19 UTCEPSS rescore
  19. 2026-08-29 12:43 UTCOSV refresh
  20. 2026-08-28 21:38 UTCEPSS rescore
  21. 2026-08-27 14:22 UTCEPSS rescore
  22. 2026-08-26 14:43 UTCEPSS rescore
  23. 2026-08-25 13:46 UTCEPSS rescore
  24. 2026-08-23 00:17 UTCEPSS rescore
  25. 2026-08-21 23:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 22:53 UTCEPSS rescore
  2. 2026-08-19 17:01 UTCEPSS rescore
  3. 2026-08-18 13:45 UTCEPSS rescore
  4. 2026-08-17 13:44 UTCEPSS rescore
  5. 2026-08-16 14:53 UTCEPSS rescore
  6. 2026-08-16 02:12 UTCEPSS rescore
  7. 2026-08-15 01:27 UTCEPSS rescore
  8. 2026-08-13 21:58 UTCEPSS rescore
  9. 2026-08-13 00:23 UTCGHSA enrichment
  10. 2026-08-13 00:06 UTCEG score recompute
  11. 2026-08-13 00:06 UTCGHSA enrichment
  12. 2026-08-12 13:48 UTCEPSS rescore
  13. 2026-08-09 14:09 UTCOSV refresh
  14. 2026-08-09 13:44 UTCEPSS rescore
  15. 2026-08-09 13:44 UTCEPSS rescore
  16. 2026-08-08 16:34 UTCEPSS rescore
  17. 2026-08-07 16:24 UTCEPSS rescore
  18. 2026-08-06 13:44 UTCEPSS rescore
  19. 2026-08-05 19:15 UTCEPSS rescore
  20. 2026-08-04 15:07 UTCEPSS rescore
  21. 2026-08-04 10:35 UTCEPSS rescore
  22. 2026-08-03 10:33 UTCEPSS rescore
  23. 2026-08-02 02:24 UTCEPSS rescore
  24. 2026-08-01 04:13 UTCEPSS rescore
  25. 2026-08-01 04:13 UTCEPSS rescore
  26. 2026-07-30 16:25 UTCEPSS rescore
  27. 2026-07-30 01:28 UTCEPSS rescore
  28. 2026-07-28 15:34 UTCEPSS rescore
  29. 2026-07-26 14:52 UTCEPSS rescore
  30. 2026-07-26 14:52 UTCEPSS rescore
  31. 2026-07-25 14:16 UTCEPSS rescore
  32. 2026-07-24 14:41 UTCOSV refresh
  33. 2026-07-24 14:15 UTCEPSS rescore
  34. 2026-07-23 14:16 UTCEPSS rescore
  35. 2026-07-23 14:16 UTCEPSS rescore
  36. 2026-07-23 02:16 UTCEG score recompute
  37. 2026-07-22 23:04 UTCEG score recompute
  38. 2026-07-22 14:06 UTCEPSS rescore
  39. 2026-07-22 14:06 UTCEPSS rescore
  40. 2026-07-21 15:23 UTCEPSS rescore
  41. 2026-07-21 15:23 UTCEPSS rescore
  42. 2026-07-20 17:05 UTCEPSS rescore
  43. 2026-07-19 14:29 UTCEPSS rescore
  44. 2026-07-19 14:29 UTCEPSS rescore
  45. 2026-07-19 02:27 UTCEPSS rescore
  46. 2026-07-19 02:27 UTCEPSS rescore
  47. 2026-07-18 10:03 UTCEPSS rescore
  48. 2026-07-18 10:03 UTCEPSS rescore
  49. 2026-07-16 17:00 UTCEPSS rescore
  50. 2026-07-15 16:56 UTCEPSS rescore
  51. 2026-07-15 16:56 UTCEPSS rescore
  52. 2026-07-15 01:58 UTCEPSS rescore
  53. 2026-07-15 01:58 UTCEPSS rescore
  54. 2026-07-13 22:28 UTCEPSS rescore
  55. 2026-07-13 22:28 UTCEPSS rescore
  56. 2026-07-13 06:11 UTCEPSS rescore
  57. 2026-07-13 06:11 UTCEPSS rescore
  58. 2026-07-12 05:44 UTCEPSS rescore
  59. 2026-07-11 08:25 UTCEPSS rescore
  60. 2026-07-11 08:25 UTCEPSS rescore
  61. 2026-07-09 19:08 UTCEPSS rescore
  62. 2026-07-08 15:13 UTCEPSS rescore
  63. 2026-07-07 13:44 UTCEPSS rescore
  64. 2026-07-07 09:51 UTCOSV refresh
  65. 2026-07-06 16:25 UTCEPSS rescore
  66. 2026-07-06 02:21 UTCEPSS rescore
  67. 2026-07-05 02:28 UTCEPSS rescore
  68. 2026-07-04 06:29 UTCEPSS rescore
  69. 2026-07-01 15:04 UTCEPSS rescore
  70. 2026-06-30 23:21 UTCEPSS rescore
  71. 2026-06-30 23:20 UTCEPSS rescore
  72. 2026-06-29 14:04 UTCEPSS rescore
  73. 2026-06-28 14:06 UTCEPSS rescore
  74. 2026-06-28 04:54 UTCEPSS rescore
  75. 2026-06-28 04:54 UTCEPSS rescore

Frequently asked(5)

What is CVE-2022-49137?
CVE-2022-49137 is a medium vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: drm/amd/amdgpu/amdgpucs: fix refcount leak of a dmafence obj This issue takes place in an error path in amdgpucsfencetohandle_ioctl(). When info->in.what falls into default case, the function simply returns -EINVAL, forgetting to…
When was CVE-2022-49137 disclosed?
CVE-2022-49137 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49137 actively exploited?
CVE-2022-49137 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.3% of all scored CVEs.
What is the CVSS score of CVE-2022-49137?
CVE-2022-49137 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49137?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49137, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49137

Explore →

Is Your Infrastructure Affected by CVE-2022-49137?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.