From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98721: mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ
Date: Sun, 18 Oct 2026 17:44:56 +0200 [thread overview]
Message-ID: <2026101809-CVE-2026-98721-6fbd@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ
The Cadence NAND interrupt handler uses both the IRQ lock and completion
object. Registering the IRQ before initializing them leaves a window in
which a pending interrupt can access uninitialized synchronization state.
Initialize them before registering the handler.
The Linux kernel CVE team has assigned CVE-2026-98721 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.5 with commit ec4ba01e894d3165e4d1ccbef782ef5593b708b4 and fixed in 6.12.113 with commit 24319f25b641e55f84e55455092a39a2485c78d4
Issue introduced in 5.5 with commit ec4ba01e894d3165e4d1ccbef782ef5593b708b4 and fixed in 6.18.56 with commit 1ed0ccd5649154bfc00ab11c59262d4f42515252
Issue introduced in 5.5 with commit ec4ba01e894d3165e4d1ccbef782ef5593b708b4 and fixed in 7.2.10 with commit bbd87eca5407288f2b63ff9357c611cd57e7e640
Issue introduced in 5.5 with commit ec4ba01e894d3165e4d1ccbef782ef5593b708b4 and fixed in 7.3-rc6 with commit 21f027016b1290d13c30b198ae7a00e6b3d1d5a5
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-98721
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/cadence-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/24319f25b641e55f84e55455092a39a2485c78d4
https://git.kernel.org/stable/c/1ed0ccd5649154bfc00ab11c59262d4f42515252
https://git.kernel.org/stable/c/bbd87eca5407288f2b63ff9357c611cd57e7e640
https://git.kernel.org/stable/c/21f027016b1290d13c30b198ae7a00e6b3d1d5a5
reply other threads:[~2026-10-18 15:54 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=2026101809-CVE-2026-98721-6fbd@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.