From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2021-47020: soundwire: stream: fix memory leak in stream config error path
Date: Thu, 29 Feb 2024 23:31:19 +0100 [thread overview]
Message-ID: <2024022920-CVE-2021-47020-78d9@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
soundwire: stream: fix memory leak in stream config error path
When stream config is failed, master runtime will release all
slave runtime in the slave_rt_list, but slave runtime is not
added to the list at this time. This patch frees slave runtime
in the config error path to fix the memory leak.
The Linux kernel CVE team has assigned CVE-2021-47020 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.18 with commit 89e590535f32 and fixed in 4.19.191 with commit 342260fe8210
Issue introduced in 4.18 with commit 89e590535f32 and fixed in 5.4.119 with commit 870533403ffa
Issue introduced in 4.18 with commit 89e590535f32 and fixed in 5.10.37 with commit 7c468deae306
Issue introduced in 4.18 with commit 89e590535f32 and fixed in 5.11.21 with commit 2f17ac005b32
Issue introduced in 4.18 with commit 89e590535f32 and fixed in 5.12.4 with commit effd2bd62b41
Issue introduced in 4.18 with commit 89e590535f32 and fixed in 5.13 with commit 48f17f96a817
Please see https://www.kernel.org or 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-2021-47020
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/soundwire/stream.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/342260fe821047c3d515e3d28085d73fbdce3e80
https://git.kernel.org/stable/c/870533403ffa28ff63e173045fc5369365642002
https://git.kernel.org/stable/c/7c468deae306d0cbbd539408c26cfec04c66159a
https://git.kernel.org/stable/c/2f17ac005b320c85d686088cfd4c2e7017912b88
https://git.kernel.org/stable/c/effd2bd62b416f6629e18e3ce077c60de14cfdea
https://git.kernel.org/stable/c/48f17f96a81763c7c8bf5500460a359b9939359f
reply other threads:[~2024-02-29 22:31 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=2024022920-CVE-2021-47020-78d9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).