From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49466: regulator: scmi: Fix refcount leak in scmi_regulator_probe
Date: Wed, 26 Feb 2025 03:12:20 +0100 [thread overview]
Message-ID: <2025022601-CVE-2022-49466-d3cd@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
regulator: scmi: Fix refcount leak in scmi_regulator_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-49466 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.11 with commit 0fbeae70ee7ce98e18a47337cd1f205dd88589e9 and fixed in 5.15.46 with commit 9ebbfa73d69909b7c737f599fd4ebd42318fc881
Issue introduced in 5.11 with commit 0fbeae70ee7ce98e18a47337cd1f205dd88589e9 and fixed in 5.17.14 with commit 299a002161c7bfb72e99ba45e5b660aecc344ea0
Issue introduced in 5.11 with commit 0fbeae70ee7ce98e18a47337cd1f205dd88589e9 and fixed in 5.18.3 with commit 4a59c763ef9b68c711dc2fd2ef4a6648da5480ee
Issue introduced in 5.11 with commit 0fbeae70ee7ce98e18a47337cd1f205dd88589e9 and fixed in 5.19 with commit 68d6c8476fd4f448e70e0ab31ff972838ac41dae
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-49466
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/regulator/scmi-regulator.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/9ebbfa73d69909b7c737f599fd4ebd42318fc881
https://git.kernel.org/stable/c/299a002161c7bfb72e99ba45e5b660aecc344ea0
https://git.kernel.org/stable/c/4a59c763ef9b68c711dc2fd2ef4a6648da5480ee
https://git.kernel.org/stable/c/68d6c8476fd4f448e70e0ab31ff972838ac41dae
reply other threads:[~2025-02-26 2:15 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-49466-d3cd@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.