[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022609-CVE-2022-49150-57a2@gregkh>
Date: Wed, 26 Feb 2025 02:55:55 +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-49150: rtc: gamecube: Fix refcount leak in gamecube_rtc_read_offset_from_sram
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
rtc: gamecube: Fix refcount leak in gamecube_rtc_read_offset_from_sram
The of_find_compatible_node() function returns a node pointer with
refcount incremented, We should use of_node_put() on it when done
Add the missing of_node_put() to release the refcount.
The Linux kernel CVE team has assigned CVE-2022-49150 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.17 with commit 86559400b3ef9de93ba50523cffe767c35cd531a and fixed in 5.17.2 with commit de66e4f28dfd11f954966c447b4430529ed040a2
Issue introduced in 5.17 with commit 86559400b3ef9de93ba50523cffe767c35cd531a and fixed in 5.18 with commit 4b2dc39ca024990abe36ad5d145c4fe0c06afd34
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-49150
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/rtc/rtc-gamecube.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/de66e4f28dfd11f954966c447b4430529ed040a2
https://git.kernel.org/stable/c/4b2dc39ca024990abe36ad5d145c4fe0c06afd34
Powered by blists - more mailing lists