From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49463: thermal/drivers/imx_sc_thermal: Fix refcount leak in imx_sc_thermal_probe
Date: Wed, 26 Feb 2025 03:12:17 +0100 [thread overview]
Message-ID: <2025022601-CVE-2022-49463-ae19@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
thermal/drivers/imx_sc_thermal: Fix refcount leak in imx_sc_thermal_probe
of_find_node_by_name() 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-49463 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.7 with commit e20db70dba1c0783b9878ce37171ad560b1ebaf3 and fixed in 5.10.121 with commit 8bbf522a2c51ef939d0e8835e236bfcd252193af
Issue introduced in 5.7 with commit e20db70dba1c0783b9878ce37171ad560b1ebaf3 and fixed in 5.15.46 with commit 3ade442ea5d3512a3c67984489ab4d8a6fb3b29f
Issue introduced in 5.7 with commit e20db70dba1c0783b9878ce37171ad560b1ebaf3 and fixed in 5.17.14 with commit 0ec10303c10833c1bcba7a1bde2f297e494d5464
Issue introduced in 5.7 with commit e20db70dba1c0783b9878ce37171ad560b1ebaf3 and fixed in 5.18.3 with commit ec0925b731697db7cab5944a3e55d2d58bb3d075
Issue introduced in 5.7 with commit e20db70dba1c0783b9878ce37171ad560b1ebaf3 and fixed in 5.19 with commit 09700c504d8e63faffd2a2235074e8c5d130cb8f
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-49463
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/thermal/imx_sc_thermal.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/8bbf522a2c51ef939d0e8835e236bfcd252193af
https://git.kernel.org/stable/c/3ade442ea5d3512a3c67984489ab4d8a6fb3b29f
https://git.kernel.org/stable/c/0ec10303c10833c1bcba7a1bde2f297e494d5464
https://git.kernel.org/stable/c/ec0925b731697db7cab5944a3e55d2d58bb3d075
https://git.kernel.org/stable/c/09700c504d8e63faffd2a2235074e8c5d130cb8f
reply other threads:[~2025-02-26 2:14 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=2025022601-CVE-2022-49463-ae19@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.