CVE-2022-50758
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A memory leak in the Linux kernel's vt6655 driver occurs when ring buffer allocation fails, because the cleanup loop skips index 0.
Vulnerability
In the Linux kernel's staging vt6655 wireless driver, the function device_init_td0_ring allocates memory for the td_info member of each ring entry priv->apTD0Rings[i] as i increases from 0. If an allocation fails partway through, the cleanup loop frees previously allocated entries in reverse order, but it incorrectly omits the case i=0, leaving that entry's memory allocated and causing a memory leak [1][2][3].
Exploitation
This is a local vulnerability that can be triggered during driver initialization when memory is scarce. An attacker with local access or the ability to exhaust system memory could cause the allocation to fail, leading to the leak. No special privileges beyond the ability to load or initialize the vt6655 driver are required.
Impact
A successful trigger results in a small memory leak each time the driver is initialized under low-memory conditions. Repeated exploitation could exhaust kernel memory, potentially leading to a denial-of-service (DoS) condition on the affected system.
Mitigation
The fix, which modifies the cleanup loop to include i=0, has been applied to the Linux kernel stable tree [1][2][3]. Users should update to a kernel version containing the commit to eliminate the leak.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
7e741e38aa98716a45e78a6871b3cebeca99eff8551d411f1fb5f569bcda8cfdf13925861c8ff91535880Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
7- git.kernel.org/stable/c/16a45e78a687eb6c69acc4e62b94b6508b0bfbdanvd
- git.kernel.org/stable/c/1b3cebeca99e8e0aa4fa57faac8dbf41e967317anvd
- git.kernel.org/stable/c/c8ff91535880d41b49699b3829fb6151942de29envd
- git.kernel.org/stable/c/cfdf139258614ef65b0f68b857ada5328fb7c0e5nvd
- git.kernel.org/stable/c/e741e38aa98704fbb959650ecd270b71b2670680nvd
- git.kernel.org/stable/c/fb5f569bcda8f87bd47d8030bfae343d757fa3eanvd
- git.kernel.org/stable/c/ff8551d411f12b5abc5ca929ab87643afa8a9588nvd
News mentions
0No linked articles in our index yet.