From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49680: ARM: exynos: Fix refcount leak in exynos_map_pmu
Date: Wed, 26 Feb 2025 03:24:03 +0100 [thread overview]
Message-ID: <2025022625-CVE-2022-49680-9dea@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ARM: exynos: Fix refcount leak in exynos_map_pmu
of_find_matching_node() returns a node pointer with refcount
incremented, we should use of_node_put() on it when not need anymore.
Add missing of_node_put() to avoid refcount leak.
of_node_put() checks null pointer.
The Linux kernel CVE team has assigned CVE-2022-49680 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 4.9.321 with commit 545ae5cbae839ce39bfe09828e413f1c916082de
Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 4.14.286 with commit 31d09571bb071c20f6bdc0bb7ac1ef8dd2987c04
Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 4.19.250 with commit 7571bcecf01b69f0d3ec60ca41ce5d4c75411a4a
Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 5.4.202 with commit f9b77a52937582a5b99a5a07e4ef1e2f48f87347
Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 5.10.127 with commit 68f28d52e6cbab8dcfa249cac4356d1d0573e868
Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 5.15.51 with commit d23f76018e17618559da9eea179d137362023f95
Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 5.18.8 with commit fc354856e9fad9cd36e2ad28f9da70716025055a
Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 5.19 with commit c4c79525042a4a7df96b73477feaf232fe44ae81
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-49680
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/arm/mach-exynos/exynos.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/545ae5cbae839ce39bfe09828e413f1c916082de
https://git.kernel.org/stable/c/31d09571bb071c20f6bdc0bb7ac1ef8dd2987c04
https://git.kernel.org/stable/c/7571bcecf01b69f0d3ec60ca41ce5d4c75411a4a
https://git.kernel.org/stable/c/f9b77a52937582a5b99a5a07e4ef1e2f48f87347
https://git.kernel.org/stable/c/68f28d52e6cbab8dcfa249cac4356d1d0573e868
https://git.kernel.org/stable/c/d23f76018e17618559da9eea179d137362023f95
https://git.kernel.org/stable/c/fc354856e9fad9cd36e2ad28f9da70716025055a
https://git.kernel.org/stable/c/c4c79525042a4a7df96b73477feaf232fe44ae81
reply other threads:[~2025-02-26 2:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025022625-CVE-2022-49680-9dea@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.