| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 5.18.10 and classified as critical. Affected by this issue is the function gs_usb_open. The manipulation results in memory leak.
This vulnerability is known as CVE-2022-49661. No exploit is available.
It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Linux Kernel up to 5.18.10. Affected is the function gs_usb_open. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_open/close(): fix memory leak The gs_usb driver appears to suffer from a malady common to many USB CAN adapter drivers in that it performs usb_alloc_coherent() to allocate a number of USB request blocks (URBs) for RX, and then later relies on usb_kill_anchored_urbs() to free them, but this doesn't actually free them. As a result, this may be leaking DMA memory that's been used by the driver. This commit is an adaptation of the techniques found in the esd_usb2 driver where a similar design pattern led to a memory leak. It explicitly frees the RX URBs and their DMA memory via a call to usb_free_coherent(). Since the RX URBs were allocated in the gs_can_open(), we remove them in gs_can_close() rather than in the disconnect function as was done in esd_usb2. For more information, see the 928150fad41b ("can: esd_usb2: fix memory leak").
The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2022-49661 since 02/26/2025. The exploitability is told to be easy. Technical details are known, but there is no available exploit.
The vulnerability scanner Nessus provides a plugin with the ID 232643 (SUSE SLES12 Security Update : kernel (SUSE-SU-2025:0834-1)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.9.323, 4.14.288, 4.19.252, 5.4.205, 5.10.130, 5.15.54 or 5.18.11 eliminates this vulnerability. Applying the patch 339fa9f80d3b94177a7a459c6d115d3b56007d5a/c1d806bc29ff7ffe0e2a023583c8720ed96cb0b0/d91492638b054f4a359621ef216242be5973ed6b/6f655b5e13fa4b27e915b6c209ac0da74fd75963/d0b8e223998866b3e7b2895927d4e9689b0a80d8/0e60230bc64355c80abe993d1719fdb318094e20/ffb6cc6601ec7c8fa963dcf76025df4a02f2cf5c/2bda24ef95c0311ab93bda00db40486acf30bd0a 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 (232643). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 4.9.322
- 4.14.287
- 4.19.251
- 5.4.204
- 5.10.129
- 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.15.34
- 5.15.35
- 5.15.36
- 5.15.37
- 5.15.38
- 5.15.39
- 5.15.40
- 5.15.41
- 5.15.42
- 5.15.43
- 5.15.44
- 5.15.45
- 5.15.46
- 5.15.47
- 5.15.48
- 5.15.49
- 5.15.50
- 5.15.51
- 5.15.52
- 5.15.53
- 5.18.0
- 5.18.1
- 5.18.2
- 5.18.3
- 5.18.4
- 5.18.5
- 5.18.6
- 5.18.7
- 5.18.8
- 5.18.9
- 5.18.10
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory leakCWE: CWE-401 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 232643
Nessus Name: SUSE SLES12 Security Update : kernel (SUSE-SU-2025:0834-1)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 4.9.323/4.14.288/4.19.252/5.4.205/5.10.130/5.15.54/5.18.11
Patch: 339fa9f80d3b94177a7a459c6d115d3b56007d5a/c1d806bc29ff7ffe0e2a023583c8720ed96cb0b0/d91492638b054f4a359621ef216242be5973ed6b/6f655b5e13fa4b27e915b6c209ac0da74fd75963/d0b8e223998866b3e7b2895927d4e9689b0a80d8/0e60230bc64355c80abe993d1719fdb318094e20/ffb6cc6601ec7c8fa963dcf76025df4a02f2cf5c/2bda24ef95c0311ab93bda00db40486acf30bd0a
Timeline
02/26/2025 🔍02/26/2025 🔍
02/26/2025 🔍
10/23/2025 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-49661 (🔍)
GCVE (CVE): GCVE-0-2022-49661
GCVE (VulDB): GCVE-100-297210
Entry
Created: 02/26/2025 10:48Updated: 10/23/2025 18:52
Changes: 02/26/2025 10:48 (58), 03/12/2025 18:46 (2), 10/23/2025 18:52 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.

No comments yet. Languages: en.
Please log in to comment.