From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49502: media: rga: fix possible memory leak in rga_probe
Date: Wed, 26 Feb 2025 03:12:56 +0100 [thread overview]
Message-ID: <2025022608-CVE-2022-49502-0cba@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: rga: fix possible memory leak in rga_probe
rga->m2m_dev needs to be freed when rga_probe fails.
The Linux kernel CVE team has assigned CVE-2022-49502 to this issue.
Affected and fixed versions
===========================
Fixed in 5.10.121 with commit 8ddc89437ccefa18279918c19a61fd81527f40b9
Fixed in 5.15.46 with commit eeb4819e94aa69767b9e5591e70c63e8b7c5786a
Fixed in 5.17.14 with commit b7bbca4d08471bc8404a946bab1aa017dd05199b
Fixed in 5.18.3 with commit 1cdc768468c25d6b10ab83ec1efd4a8554532d69
Fixed in 5.19 with commit a71eb6025305192e646040cd76ccacb5bd48a1b5
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-49502
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/rockchip/rga/rga.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/8ddc89437ccefa18279918c19a61fd81527f40b9
https://git.kernel.org/stable/c/eeb4819e94aa69767b9e5591e70c63e8b7c5786a
https://git.kernel.org/stable/c/b7bbca4d08471bc8404a946bab1aa017dd05199b
https://git.kernel.org/stable/c/1cdc768468c25d6b10ab83ec1efd4a8554532d69
https://git.kernel.org/stable/c/a71eb6025305192e646040cd76ccacb5bd48a1b5
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=2025022608-CVE-2022-49502-0cba@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.