[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022657-CVE-2022-49437-7624@gregkh>
Date: Wed, 26 Feb 2025 03:11:51 +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-49437: powerpc/xive: Fix refcount leak in xive_spapr_init
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
powerpc/xive: Fix refcount leak in xive_spapr_init
of_find_compatible_node() returns a node pointer with refcount
incremented, we should use of_node_put() on it when done.
Add missing of_node_put() to avoid refcount leak.
The Linux kernel CVE team has assigned CVE-2022-49437 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.14 with commit eac1e731b59ee3b5f5e641a7765c7ed41ed26226 and fixed in 5.15.46 with commit 65f11ccdd746e0e7f0b469cc989ba43d4f30ecfe
Issue introduced in 4.14 with commit eac1e731b59ee3b5f5e641a7765c7ed41ed26226 and fixed in 5.17.14 with commit 6e806485d851986a2445267608f27cb4ba2ed774
Issue introduced in 4.14 with commit eac1e731b59ee3b5f5e641a7765c7ed41ed26226 and fixed in 5.18.3 with commit cc62dde2a5f4ba14016fd9caec76f08d388f4b9c
Issue introduced in 4.14 with commit eac1e731b59ee3b5f5e641a7765c7ed41ed26226 and fixed in 5.19 with commit 1d1fb9618bdd5a5fbf9a9eb75133da301d33721c
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-49437
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:
arch/powerpc/sysdev/xive/spapr.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/65f11ccdd746e0e7f0b469cc989ba43d4f30ecfe
https://git.kernel.org/stable/c/6e806485d851986a2445267608f27cb4ba2ed774
https://git.kernel.org/stable/c/cc62dde2a5f4ba14016fd9caec76f08d388f4b9c
https://git.kernel.org/stable/c/1d1fb9618bdd5a5fbf9a9eb75133da301d33721c
Powered by blists - more mailing lists