linux-cve-announce - CVE-2022-49108: clk: mediatek: Fix memory leaks on probe

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: <2025022601-CVE-2022-49108-328f@gregkh>
Date: Wed, 26 Feb 2025 02:55:13 +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-49108: clk: mediatek: Fix memory leaks on probe

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

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

clk: mediatek: Fix memory leaks on probe

Handle the error branches to free memory where required.

Addresses-Coverity-ID: 1491825 ("Resource leak")

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


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

	Fixed in 5.16.20 with commit c6a0b413398588fc2d8b174a79ea715b66413fca
	Fixed in 5.17.3 with commit 02742d1d5c95cff8b6e9379aae4ab12674f7265d
	Fixed in 5.18 with commit 7a688c91d3fd54c53e7a9edd6052cdae98dd99d8

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-49108
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/clk/mediatek/clk-mt8192.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/c6a0b413398588fc2d8b174a79ea715b66413fca
	https://git.kernel.org/stable/c/02742d1d5c95cff8b6e9379aae4ab12674f7265d
	https://git.kernel.org/stable/c/7a688c91d3fd54c53e7a9edd6052cdae98dd99d8