[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061842-CVE-2022-50208-f4e9@gregkh>
Date: Wed, 18 Jun 2025 13:04:33 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50208: soc: amlogic: Fix refcount leak in meson-secure-pwrc.c
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
soc: amlogic: Fix refcount leak in meson-secure-pwrc.c
In meson_secure_pwrc_probe(), there is a refcount leak in one fail
path.
The Linux kernel CVE team has assigned CVE-2022-50208 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.7 with commit b3dde5013e13d44799b3477cd0bf0c9ad34fe5e9 and fixed in 5.10.137 with commit 80c469e63bfa9a5a8114952bffc6a7d241e7497e
Issue introduced in 5.7 with commit b3dde5013e13d44799b3477cd0bf0c9ad34fe5e9 and fixed in 5.15.61 with commit f370fbbd3151c1c87d1e976c8964cb6cc46f2e00
Issue introduced in 5.7 with commit b3dde5013e13d44799b3477cd0bf0c9ad34fe5e9 and fixed in 5.18.18 with commit 5509d07a9364b75b28055bf2d89289e4e5269929
Issue introduced in 5.7 with commit b3dde5013e13d44799b3477cd0bf0c9ad34fe5e9 and fixed in 5.19.2 with commit d1fbbb5ded714b6610a16ec3d7e271a55291ccc4
Issue introduced in 5.7 with commit b3dde5013e13d44799b3477cd0bf0c9ad34fe5e9 and fixed in 6.0 with commit d18529a4c12f66d83daac78045ea54063bd43257
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-50208
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/soc/amlogic/meson-secure-pwrc.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/80c469e63bfa9a5a8114952bffc6a7d241e7497e
https://git.kernel.org/stable/c/f370fbbd3151c1c87d1e976c8964cb6cc46f2e00
https://git.kernel.org/stable/c/5509d07a9364b75b28055bf2d89289e4e5269929
https://git.kernel.org/stable/c/d1fbbb5ded714b6610a16ec3d7e271a55291ccc4
https://git.kernel.org/stable/c/d18529a4c12f66d83daac78045ea54063bd43257
Powered by blists - more mailing lists