linux-cve-announce - CVE-2022-50658: cpufreq: qcom: fix memory leak in error path

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: <2025120941-CVE-2022-50658-77b4@gregkh>
Date: Tue,  9 Dec 2025 10:30:43 +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-50658: cpufreq: qcom: fix memory leak in error path

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

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

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

cpufreq: qcom: fix memory leak in error path

If for some reason the speedbin length is incorrect, then there is a
memory leak in the error path because we never free the speedbin buffer.
This commit fixes the error path to always free the speedbin buffer.

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


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

	Issue introduced in 5.7 with commit a8811ec764f95a04ba82f6f457e28c5e9e36e36b and fixed in 5.10.152 with commit e55feb31df3fc78b880d6e9d4b5853f05c974833
	Issue introduced in 5.7 with commit a8811ec764f95a04ba82f6f457e28c5e9e36e36b and fixed in 5.15.76 with commit b5606e3ab1f7cc00d89903f4a11fe57747bb3a68
	Issue introduced in 5.7 with commit a8811ec764f95a04ba82f6f457e28c5e9e36e36b and fixed in 6.0.6 with commit b6ea267e0c6bdf5463358e2a2e5280cfa6cacc48
	Issue introduced in 5.7 with commit a8811ec764f95a04ba82f6f457e28c5e9e36e36b and fixed in 6.1 with commit 9f42cf54403a42cb092636804d2628d8ecf71e75

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-50658
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-nvmem.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/e55feb31df3fc78b880d6e9d4b5853f05c974833
	https://git.kernel.org/stable/c/b5606e3ab1f7cc00d89903f4a11fe57747bb3a68
	https://git.kernel.org/stable/c/b6ea267e0c6bdf5463358e2a2e5280cfa6cacc48
	https://git.kernel.org/stable/c/9f42cf54403a42cb092636804d2628d8ecf71e75