From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89952: mtd: rawnand: validate ONFI extended parameter page sections
Date: Wed, 16 Sep 2026 11:31:22 +0100 [thread overview]
Message-ID: <2026091649-CVE-2026-89952-c477@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mtd: rawnand: validate ONFI extended parameter page sections
nand_flash_detect_ext_param_page() allocates the length declared by the
ONFI parameter page, then treats the data as a fixed header followed by
variable-length sections. It reads that header and advances over sections
without first proving that the fixed page and each current section fit in
the allocation.
Reject pages shorter than the fixed header, track the remaining variable
area while walking sections, and require the ECC section to contain every
field read from struct onfi_ext_ecc_info. Use device-scoped diagnostics
that identify the malformed ONFI section.
The Linux kernel CVE team has assigned CVE-2026-89952 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.12 with commit 6dcbe0cdd83fb5f77be4f44c9e06c535281c375a and fixed in 5.10.270 with commit 1bf148fabe6463422195b7cc43b3412533f1dc21
Issue introduced in 3.12 with commit 6dcbe0cdd83fb5f77be4f44c9e06c535281c375a and fixed in 5.15.221 with commit c7df90bbda71549bfd981bf478ad04ddfccf4e0d
Issue introduced in 3.12 with commit 6dcbe0cdd83fb5f77be4f44c9e06c535281c375a and fixed in 6.1.188 with commit 86948f81964e40cd6472d76a6371e4f297d84db0
Issue introduced in 3.12 with commit 6dcbe0cdd83fb5f77be4f44c9e06c535281c375a and fixed in 6.6.157 with commit ddb6ddf5be7429bb98b3368c883be51f00b31678
Issue introduced in 3.12 with commit 6dcbe0cdd83fb5f77be4f44c9e06c535281c375a and fixed in 6.12.110 with commit 12a63a0f0d17b2d26211b2524ded91a67dd5c99c
Issue introduced in 3.12 with commit 6dcbe0cdd83fb5f77be4f44c9e06c535281c375a and fixed in 6.18.51 with commit c8f86e375b39cada09fd8cb33dd3bb3641e84a62
Issue introduced in 3.12 with commit 6dcbe0cdd83fb5f77be4f44c9e06c535281c375a and fixed in 7.2.5 with commit 23e747fe585830c43095c37c85b2757231c6917f
Issue introduced in 3.12 with commit 6dcbe0cdd83fb5f77be4f44c9e06c535281c375a and fixed in 7.3-rc1 with commit e5e415262330bd70f983e091d8919d9dcd99e475
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-2026-89952
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/nand_onfi.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/1bf148fabe6463422195b7cc43b3412533f1dc21
https://git.kernel.org/stable/c/c7df90bbda71549bfd981bf478ad04ddfccf4e0d
https://git.kernel.org/stable/c/86948f81964e40cd6472d76a6371e4f297d84db0
https://git.kernel.org/stable/c/ddb6ddf5be7429bb98b3368c883be51f00b31678
https://git.kernel.org/stable/c/12a63a0f0d17b2d26211b2524ded91a67dd5c99c
https://git.kernel.org/stable/c/c8f86e375b39cada09fd8cb33dd3bb3641e84a62
https://git.kernel.org/stable/c/23e747fe585830c43095c37c85b2757231c6917f
https://git.kernel.org/stable/c/e5e415262330bd70f983e091d8919d9dcd99e475
reply other threads:[~2026-09-16 10:40 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=2026091649-CVE-2026-89952-c477@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@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.