[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122454-CVE-2022-50758-800b@gregkh>
Date: Wed, 24 Dec 2025 14:06:09 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50758: staging: vt6655: fix potential memory leak
From: Greg Kroah-Hartman <gregkh@...nel.org>
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.
The Linux kernel CVE team has assigned CVE-2022-50758 to this issue.
Affected and fixed versions
===========================
Fixed in 4.19.262 with commit e741e38aa98704fbb959650ecd270b71b2670680
Fixed in 5.4.220 with commit 16a45e78a687eb6c69acc4e62b94b6508b0bfbda
Fixed in 5.10.150 with commit 1b3cebeca99e8e0aa4fa57faac8dbf41e967317a
Fixed in 5.15.75 with commit ff8551d411f12b5abc5ca929ab87643afa8a9588
Fixed in 5.19.17 with commit fb5f569bcda8f87bd47d8030bfae343d757fa3ea
Fixed in 6.0.3 with commit cfdf139258614ef65b0f68b857ada5328fb7c0e5
Fixed in 6.1 with commit c8ff91535880d41b49699b3829fb6151942de29e
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2022-50758
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/staging/vt6655/device_main.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/e741e38aa98704fbb959650ecd270b71b2670680
https://git.kernel.org/stable/c/16a45e78a687eb6c69acc4e62b94b6508b0bfbda
https://git.kernel.org/stable/c/1b3cebeca99e8e0aa4fa57faac8dbf41e967317a
https://git.kernel.org/stable/c/ff8551d411f12b5abc5ca929ab87643afa8a9588
https://git.kernel.org/stable/c/fb5f569bcda8f87bd47d8030bfae343d757fa3ea
https://git.kernel.org/stable/c/cfdf139258614ef65b0f68b857ada5328fb7c0e5
https://git.kernel.org/stable/c/c8ff91535880d41b49699b3829fb6151942de29e
Powered by blists - more mailing lists