Linux Kernel up to 6.0.2 staging device_init_td0_ring memory leak

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Linux Kernel up to 6.0.2. This vulnerability affects the function device_init_td0_ring of the component staging. The manipulation leads to memory leak.
This vulnerability is traded as CVE-2022-50758. There is no exploit available.
It is recommended to upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 6.0.2 and classified as critical. This issue affects the function device_init_td0_ring of the component staging. The manipulation with an unknown input leads to a memory leak vulnerability. Using CWE to declare the problem leads to CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. Impacted is availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: staging: vt6655: fix potential memory leak In function device_init_td0_ring, memory is allocated for member td_info of priv->apTD0Rings[i], with i increasing from 0. In case of allocation failure, the memory is freed in reversed order, with i decreasing to 0. However, the case i=0 is left out and thus memory is leaked. Modify the memory freeing loop to include the case i=0.
It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2022-50758 since 12/24/2025. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability scanner Nessus provides a plugin with the ID 280004 (Linux Distros Unpatched Vulnerability : CVE-2022-50758), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17 or 6.0.3 eliminates this vulnerability. Applying the patch e741e38aa98704fbb959650ecd270b71b2670680/16a45e78a687eb6c69acc4e62b94b6508b0bfbda/1b3cebeca99e8e0aa4fa57faac8dbf41e967317a/ff8551d411f12b5abc5ca929ab87643afa8a9588/fb5f569bcda8f87bd47d8030bfae343d757fa3ea/cfdf139258614ef65b0f68b857ada5328fb7c0e5/c8ff91535880d41b49699b3829fb6151942de29e 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 databases at Tenable (280004) and CERT Bund (WID-SEC-2025-2929). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- Open Source Linux Kernel
Product
Type
Vendor
Name
Version
- 4.19.261
- 5.4.219
- 5.10.149
- 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.15.54
- 5.15.55
- 5.15.56
- 5.15.57
- 5.15.58
- 5.15.59
- 5.15.60
- 5.15.61
- 5.15.62
- 5.15.63
- 5.15.64
- 5.15.65
- 5.15.66
- 5.15.67
- 5.15.68
- 5.15.69
- 5.15.70
- 5.15.71
- 5.15.72
- 5.15.73
- 5.15.74
- 5.19.0
- 5.19.1
- 5.19.2
- 5.19.3
- 5.19.4
- 5.19.5
- 5.19.6
- 5.19.7
- 5.19.8
- 5.19.9
- 5.19.10
- 5.19.11
- 5.19.12
- 5.19.13
- 5.19.14
- 5.19.15
- 5.19.16
- 6.0.0
- 6.0.1
- 6.0.2
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: No
Local: No
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: 280004
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2022-50758
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 4.19.262/5.4.220/5.10.150/5.15.75/5.19.17/6.0.3
Patch: e741e38aa98704fbb959650ecd270b71b2670680/16a45e78a687eb6c69acc4e62b94b6508b0bfbda/1b3cebeca99e8e0aa4fa57faac8dbf41e967317a/ff8551d411f12b5abc5ca929ab87643afa8a9588/fb5f569bcda8f87bd47d8030bfae343d757fa3ea/cfdf139258614ef65b0f68b857ada5328fb7c0e5/c8ff91535880d41b49699b3829fb6151942de29e
Timeline
12/24/2025 Advisory disclosed12/24/2025 CVE reserved
12/24/2025 VulDB entry created
04/21/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-50758 (🔒)
GCVE (CVE): GCVE-0-2022-50758
GCVE (VulDB): GCVE-100-338099
CERT Bund: WID-SEC-2025-2929 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 12/24/2025 15:07Updated: 04/21/2026 07:37
Changes: 12/24/2025 15:07 (59), 12/27/2025 22:03 (2), 12/29/2025 18:59 (7), 04/21/2026 07:37 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.