From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49487: mtd: rawnand: intel: fix possible null-ptr-deref in ebu_nand_probe()
Date: Wed, 26 Feb 2025 03:12:41 +0100 [thread overview]
Message-ID: <2025022605-CVE-2022-49487-c710@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mtd: rawnand: intel: fix possible null-ptr-deref in ebu_nand_probe()
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.
The Linux kernel CVE team has assigned CVE-2022-49487 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.11 with commit 0b1039f016e8a37c779a4aee362cb2100ebb1cfd and fixed in 5.15.46 with commit e5b1e419cdb6dd8709eb05ed34039a3ded8e6003
Issue introduced in 5.11 with commit 0b1039f016e8a37c779a4aee362cb2100ebb1cfd and fixed in 5.17.14 with commit daa5166450b447415aeeaac0199e445bae7bd0f2
Issue introduced in 5.11 with commit 0b1039f016e8a37c779a4aee362cb2100ebb1cfd and fixed in 5.18.3 with commit f8e262eb7575a4a2412f30f7a1b293875aceba80
Issue introduced in 5.11 with commit 0b1039f016e8a37c779a4aee362cb2100ebb1cfd and fixed in 5.19 with commit ddf66aefd685fd46500b9917333e1b1e118276dc
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-49487
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/mtd/nand/raw/intel-nand-controller.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/e5b1e419cdb6dd8709eb05ed34039a3ded8e6003
https://git.kernel.org/stable/c/daa5166450b447415aeeaac0199e445bae7bd0f2
https://git.kernel.org/stable/c/f8e262eb7575a4a2412f30f7a1b293875aceba80
https://git.kernel.org/stable/c/ddf66aefd685fd46500b9917333e1b1e118276dc
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=2025022605-CVE-2022-49487-c710@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.