From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49482: ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe
Date: Wed, 26 Feb 2025 03:12:36 +0100 [thread overview]
Message-ID: <2025022604-CVE-2022-49482-b33c@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe
of_parse_phandle() returns a node pointer with refcount
incremented, we should use of_node_put() on it when done.
The Linux kernel CVE team has assigned CVE-2022-49482 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.5 with commit 08641c7c74dddfcd726512edfaa3b4cbe42e523e and fixed in 4.9.318 with commit c933829cbf3338b684869e6c4c8931abf5d68fbd
Issue introduced in 3.5 with commit 08641c7c74dddfcd726512edfaa3b4cbe42e523e and fixed in 4.14.283 with commit d42601e93fce7802bb8d70dd59b60cfeefa20469
Issue introduced in 3.5 with commit 08641c7c74dddfcd726512edfaa3b4cbe42e523e and fixed in 4.19.247 with commit 30d110ca703ce60162ec337aa564a3e4da30715f
Issue introduced in 3.5 with commit 08641c7c74dddfcd726512edfaa3b4cbe42e523e and fixed in 5.4.198 with commit 18b907ff0ae4bf20120aae1538f7156b9d08e3a7
Issue introduced in 3.5 with commit 08641c7c74dddfcd726512edfaa3b4cbe42e523e and fixed in 5.10.121 with commit 2a0da7641e1f17a744ac7b3f76471388c97b63dc
Issue introduced in 3.5 with commit 08641c7c74dddfcd726512edfaa3b4cbe42e523e and fixed in 5.15.46 with commit 24491124406666bf0dcb9ee10c5575c6ce6a1730
Issue introduced in 3.5 with commit 08641c7c74dddfcd726512edfaa3b4cbe42e523e and fixed in 5.17.14 with commit 4e2a1bcc51bdebed48176f6e88c150f175983f9c
Issue introduced in 3.5 with commit 08641c7c74dddfcd726512edfaa3b4cbe42e523e and fixed in 5.18.3 with commit d855505851ee8ba666eb204149b49f906130dc17
Issue introduced in 3.5 with commit 08641c7c74dddfcd726512edfaa3b4cbe42e523e and fixed in 5.19 with commit 2be84f73785fa9ed6443e3c5b158730266f1c2ee
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-49482
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:
sound/soc/mxs/mxs-saif.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/c933829cbf3338b684869e6c4c8931abf5d68fbd
https://git.kernel.org/stable/c/d42601e93fce7802bb8d70dd59b60cfeefa20469
https://git.kernel.org/stable/c/30d110ca703ce60162ec337aa564a3e4da30715f
https://git.kernel.org/stable/c/18b907ff0ae4bf20120aae1538f7156b9d08e3a7
https://git.kernel.org/stable/c/2a0da7641e1f17a744ac7b3f76471388c97b63dc
https://git.kernel.org/stable/c/24491124406666bf0dcb9ee10c5575c6ce6a1730
https://git.kernel.org/stable/c/4e2a1bcc51bdebed48176f6e88c150f175983f9c
https://git.kernel.org/stable/c/d855505851ee8ba666eb204149b49f906130dc17
https://git.kernel.org/stable/c/2be84f73785fa9ed6443e3c5b158730266f1c2ee
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=2025022604-CVE-2022-49482-b33c@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.