linux-cve-announce - CVE-2022-50637: cpufreq: qcom-hw: Fix memory leak in qcom_cpufreq_hw_read

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025120935-CVE-2022-50637-f1b4@gregkh>
Date: Tue,  9 Dec 2025 09:01:38 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50637: cpufreq: qcom-hw: Fix memory leak in qcom_cpufreq_hw_read_lut()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

cpufreq: qcom-hw: Fix memory leak in qcom_cpufreq_hw_read_lut()

If "cpu_dev" fails to get opp table in qcom_cpufreq_hw_read_lut(),
the program will return, resulting in "table" resource is not released.

The Linux kernel CVE team has assigned CVE-2022-50637 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.9 with commit 51c843cf77bb52db6df947c4fedcfc62ae3b7b30 and fixed in 5.10.163 with commit 3ef12a4a8ef5553af9c3fd2719a616637a102568
	Issue introduced in 5.9 with commit 51c843cf77bb52db6df947c4fedcfc62ae3b7b30 and fixed in 5.15.86 with commit 4ea765b10624d67407817100d381c60f53593033
	Issue introduced in 5.9 with commit 51c843cf77bb52db6df947c4fedcfc62ae3b7b30 and fixed in 6.0.16 with commit 5d430076e66bddd08612911513b36f932b0d9d6c
	Issue introduced in 5.9 with commit 51c843cf77bb52db6df947c4fedcfc62ae3b7b30 and fixed in 6.1.2 with commit 242e23be8f31ebd90525c57ee3244c28e99a1697
	Issue introduced in 5.9 with commit 51c843cf77bb52db6df947c4fedcfc62ae3b7b30 and fixed in 6.2 with commit 9901c21bcaf2f01fe5078f750d624f4ddfa8f81b

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-50637
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/qcom-cpufreq-hw.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/3ef12a4a8ef5553af9c3fd2719a616637a102568
	https://git.kernel.org/stable/c/4ea765b10624d67407817100d381c60f53593033
	https://git.kernel.org/stable/c/5d430076e66bddd08612911513b36f932b0d9d6c
	https://git.kernel.org/stable/c/242e23be8f31ebd90525c57ee3244c28e99a1697
	https://git.kernel.org/stable/c/9901c21bcaf2f01fe5078f750d624f4ddfa8f81b