CVE-2022-50758
Published Dec 24, 2025
Modified Apr 15, 2026
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.
Is your site exposed to CVE-2022-50758?
Run a free security scan — no signup, results in seconds.
References
Other References
https://git.kernel.org/stable/c/16a45e78a687eb6c69acc4e62b94b6508b0bfbda
https://git.kernel.org/stable/c/1b3cebeca99e8e0aa4fa57faac8dbf41e967317a
https://git.kernel.org/stable/c/c8ff91535880d41b49699b3829fb6151942de29e
https://git.kernel.org/stable/c/cfdf139258614ef65b0f68b857ada5328fb7c0e5
https://git.kernel.org/stable/c/e741e38aa98704fbb959650ecd270b71b2670680
https://git.kernel.org/stable/c/fb5f569bcda8f87bd47d8030bfae343d757fa3ea
https://git.kernel.org/stable/c/ff8551d411f12b5abc5ca929ab87643afa8a9588
Frequently Asked Questions
What is CVE-2022-50758? +
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.
How do I check if I'm vulnerable to CVE-2022-50758? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.