From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49050: memory: renesas-rpc-if: fix platform-device leak in error path
Date: Wed, 26 Feb 2025 02:54:15 +0100 [thread overview]
Message-ID: <2025022651-CVE-2022-49050-e12a@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
memory: renesas-rpc-if: fix platform-device leak in error path
Make sure to free the flash platform device in the event that
registration fails during probe.
The Linux kernel CVE team has assigned CVE-2022-49050 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.9 with commit ca7d8b980b67f133317525c4273e144116ee1ae5 and fixed in 5.10.112 with commit c089ffc846c85f200db34ad208338f4f81a6d82d
Issue introduced in 5.9 with commit ca7d8b980b67f133317525c4273e144116ee1ae5 and fixed in 5.15.35 with commit 05d1824a7fb43ab9adb1eb82404954af81d8c984
Issue introduced in 5.9 with commit ca7d8b980b67f133317525c4273e144116ee1ae5 and fixed in 5.17.4 with commit 66b9b707ea4dcafca92b6261c6924652914e3b73
Issue introduced in 5.9 with commit ca7d8b980b67f133317525c4273e144116ee1ae5 and fixed in 5.18 with commit b452dbf24d7d9a990d70118462925f6ee287d135
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-49050
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/memory/renesas-rpc-if.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/c089ffc846c85f200db34ad208338f4f81a6d82d
https://git.kernel.org/stable/c/05d1824a7fb43ab9adb1eb82404954af81d8c984
https://git.kernel.org/stable/c/66b9b707ea4dcafca92b6261c6924652914e3b73
https://git.kernel.org/stable/c/b452dbf24d7d9a990d70118462925f6ee287d135
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=2025022651-CVE-2022-49050-e12a@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.