From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49486: ASoC: fsl: Fix refcount leak in imx_sgtl5000_probe
Date: Wed, 26 Feb 2025 03:12:40 +0100 [thread overview]
Message-ID: <2025022605-CVE-2022-49486-cdcc@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: fsl: Fix refcount leak in imx_sgtl5000_probe
of_find_i2c_device_by_node() takes a reference,
In error paths, we should call put_device() to drop
the reference to aviod refount leak.
The Linux kernel CVE team has assigned CVE-2022-49486 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.5 with commit 81e8e4926167ab32593bbb915b45a42024ca1020 and fixed in 5.4.198 with commit 96fc3da6184af5687e153d420cd7dcdeefdd2f9a
Issue introduced in 3.5 with commit 81e8e4926167ab32593bbb915b45a42024ca1020 and fixed in 5.10.121 with commit e84aaf23ca82753d765bf84d05295d9d9c5fed29
Issue introduced in 3.5 with commit 81e8e4926167ab32593bbb915b45a42024ca1020 and fixed in 5.15.46 with commit 922bccdb1796a9e7b989f2bc6d9ada7b499a4329
Issue introduced in 3.5 with commit 81e8e4926167ab32593bbb915b45a42024ca1020 and fixed in 5.17.14 with commit 4bfbbfdb3d761323127a67d7d765abe2f77d7b21
Issue introduced in 3.5 with commit 81e8e4926167ab32593bbb915b45a42024ca1020 and fixed in 5.18.3 with commit 7f75e9f629ef54a0845b43889d8ab9dd6e280dd5
Issue introduced in 3.5 with commit 81e8e4926167ab32593bbb915b45a42024ca1020 and fixed in 5.19 with commit 41cd312dfe980af869c3503b4d38e62ed20dd3b7
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-49486
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/fsl/imx-sgtl5000.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/96fc3da6184af5687e153d420cd7dcdeefdd2f9a
https://git.kernel.org/stable/c/e84aaf23ca82753d765bf84d05295d9d9c5fed29
https://git.kernel.org/stable/c/922bccdb1796a9e7b989f2bc6d9ada7b499a4329
https://git.kernel.org/stable/c/4bfbbfdb3d761323127a67d7d765abe2f77d7b21
https://git.kernel.org/stable/c/7f75e9f629ef54a0845b43889d8ab9dd6e280dd5
https://git.kernel.org/stable/c/41cd312dfe980af869c3503b4d38e62ed20dd3b7
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=2025022605-CVE-2022-49486-cdcc@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.