Back
CVE-2022-50758
staging: vt6655: fix potential memory leak
High7.8EPSS 0.22%
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Deferred | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (6 Nov 2026)
Loading the EPSS history…
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < e741e38aa98704fbb959650ecd270b71b2670680
- affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < 16a45e78a687eb6c69acc4e62b94b6508b0bfbda
- affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < 1b3cebeca99e8e0aa4fa57faac8dbf41e967317a
- affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < ff8551d411f12b5abc5ca929ab87643afa8a9588
- affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < fb5f569bcda8f87bd47d8030bfae343d757fa3ea
- affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < cfdf139258614ef65b0f68b857ada5328fb7c0e5
- affected 5341ee0adb17d12a96dc5344e0d267cd12b52135 – < c8ff91535880d41b49699b3829fb6151942de29e
- affected 4.18
- unaffected < 4.18
- unaffected 4.19.262 – ≤ 4.19.*
- unaffected 5.4.220 – ≤ 5.4.*
- unaffected 5.10.150 – ≤ 5.10.*
- unaffected 5.15.75 – ≤ 5.15.*
- unaffected 5.19.17 – ≤ 5.19.*
- unaffected 6.0.3 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References (7)
- https://git.kernel.org/stable/c/e741e38aa98704fbb959650ecd270b71b2670680 (opens in a new tab)
- https://git.kernel.org/stable/c/16a45e78a687eb6c69acc4e62b94b6508b0bfbda (opens in a new tab)
- https://git.kernel.org/stable/c/1b3cebeca99e8e0aa4fa57faac8dbf41e967317a (opens in a new tab)
- https://git.kernel.org/stable/c/ff8551d411f12b5abc5ca929ab87643afa8a9588 (opens in a new tab)
- https://git.kernel.org/stable/c/fb5f569bcda8f87bd47d8030bfae343d757fa3ea (opens in a new tab)
- https://git.kernel.org/stable/c/cfdf139258614ef65b0f68b857ada5328fb7c0e5 (opens in a new tab)
- https://git.kernel.org/stable/c/c8ff91535880d41b49699b3829fb6151942de29e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-50758)Record last updated .