From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2021-47655: media: venus: vdec: fixed possible memory leak issue
Date: Wed, 26 Feb 2025 02:54:06 +0100 [thread overview]
Message-ID: <2025022650-CVE-2021-47655-0491@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: venus: vdec: fixed possible memory leak issue
The venus_helper_alloc_dpb_bufs() implementation allows an early return
on an error path when checking the id from ida_alloc_min() which would
not release the earlier buffer allocation.
Move the direct kfree() from the error checking of dma_alloc_attrs() to
the common fail path to ensure that allocations are released on all
error paths in this function.
Addresses-Coverity: 1494120 ("Resource leak")
The Linux kernel CVE team has assigned CVE-2021-47655 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.16 with commit 40d87aafee29fb01ce1e1868502fb2059a6a7f34 and fixed in 5.16.19 with commit 55bccafc246b2e64763a155ec454470c07a54a6e
Issue introduced in 5.16 with commit 40d87aafee29fb01ce1e1868502fb2059a6a7f34 and fixed in 5.17.2 with commit 5f89d05ba93df9c2cdfe493843f93288e55e99eb
Issue introduced in 5.16 with commit 40d87aafee29fb01ce1e1868502fb2059a6a7f34 and fixed in 5.18 with commit 8403fdd775858a7bf04868d43daea0acbe49ddfc
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-2021-47655
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/media/platform/qcom/venus/helpers.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/5cedfe8aaf1875a5305897107b7f298db4260019
https://git.kernel.org/stable/c/55bccafc246b2e64763a155ec454470c07a54a6e
https://git.kernel.org/stable/c/5f89d05ba93df9c2cdfe493843f93288e55e99eb
https://git.kernel.org/stable/c/8403fdd775858a7bf04868d43daea0acbe49ddfc
reply other threads:[~2025-02-26 1:57 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=2025022650-CVE-2021-47655-0491@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.