[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022615-CVE-2022-49621-ac28@gregkh>
Date: Wed, 26 Feb 2025 03:23:04 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49621: cpufreq: pmac32-cpufreq: Fix refcount leak bug
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
cpufreq: pmac32-cpufreq: Fix refcount leak bug
In pmac_cpufreq_init_MacRISC3(), we need to add corresponding
of_node_put() for the three node pointers whose refcount have
been incremented by of_find_node_by_name().
The Linux kernel CVE team has assigned CVE-2022-49621 to this issue.
Affected and fixed versions
===========================
Fixed in 4.9.324 with commit 4f242486bf46d314b2e3838cc64b56f008a3c4d7
Fixed in 4.14.289 with commit 37c16fc2cb13a13f3c0193bfc6f2edef7d7df7d7
Fixed in 4.19.253 with commit 4585890ab2dbf455d80e254d3d859d4c1e357920
Fixed in 5.4.207 with commit 8dda30f81c751b01cd71f2cfaeef26ad4393b1d1
Fixed in 5.10.132 with commit 3ea9dbf7c2f436952bca331c6f5d72f75aca224e
Fixed in 5.15.56 with commit 57289b6601fe78c09921599b042a0b430fb420ec
Fixed in 5.18.13 with commit 4513018d0bd739097570d26a7760551cba3deb56
Fixed in 5.19 with commit ccd7567d4b6cf187fdfa55f003a9e461ee629e36
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-49621
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/cpufreq/pmac32-cpufreq.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/4f242486bf46d314b2e3838cc64b56f008a3c4d7
https://git.kernel.org/stable/c/37c16fc2cb13a13f3c0193bfc6f2edef7d7df7d7
https://git.kernel.org/stable/c/4585890ab2dbf455d80e254d3d859d4c1e357920
https://git.kernel.org/stable/c/8dda30f81c751b01cd71f2cfaeef26ad4393b1d1
https://git.kernel.org/stable/c/3ea9dbf7c2f436952bca331c6f5d72f75aca224e
https://git.kernel.org/stable/c/57289b6601fe78c09921599b042a0b430fb420ec
https://git.kernel.org/stable/c/4513018d0bd739097570d26a7760551cba3deb56
https://git.kernel.org/stable/c/ccd7567d4b6cf187fdfa55f003a9e461ee629e36
Powered by blists - more mailing lists