From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49449: pinctrl: renesas: rzn1: Fix possible null-ptr-deref in sh_pfc_map_resources()
Date: Wed, 26 Feb 2025 03:12:03 +0100 [thread overview]
Message-ID: <2025022659-CVE-2022-49449-bf9c@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
pinctrl: renesas: rzn1: Fix possible null-ptr-deref in sh_pfc_map_resources()
It will cause null-ptr-deref when using 'res', if platform_get_resource()
returns NULL, so move using 'res' after devm_ioremap_resource() that
will check it to avoid null-ptr-deref.
And use devm_platform_get_and_ioremap_resource() to simplify code.
The Linux kernel CVE team has assigned CVE-2022-49449 to this issue.
Affected and fixed versions
===========================
Fixed in 5.10.121 with commit b646e0cfeb38bf5f1944fd548f1dfa9b129fa00c
Fixed in 5.15.46 with commit c16b59d445135c8026a04e388d8b2762feaa3b3b
Fixed in 5.17.14 with commit 34c719b8fdfbd0c7c54cae56e6b0f16e9f8bf03e
Fixed in 5.18.3 with commit 01f9e02e0f13df3fd291676dc80054e977be1601
Fixed in 5.19 with commit 2f661477c2bb8068194dbba9738d05219f111c6e
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-49449
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/pinctrl/renesas/pinctrl-rzn1.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/b646e0cfeb38bf5f1944fd548f1dfa9b129fa00c
https://git.kernel.org/stable/c/c16b59d445135c8026a04e388d8b2762feaa3b3b
https://git.kernel.org/stable/c/34c719b8fdfbd0c7c54cae56e6b0f16e9f8bf03e
https://git.kernel.org/stable/c/01f9e02e0f13df3fd291676dc80054e977be1601
https://git.kernel.org/stable/c/2f661477c2bb8068194dbba9738d05219f111c6e
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=2025022659-CVE-2022-49449-bf9c@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.