From: tze.yee.ng@altera.com
To: linux-kernel@vger.kernel.org,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <mwalle@kernel.org>,
Takahiro Kuwano <takahiro.kuwano@infineon.com>,
linux-mtd@lists.infradead.org
Subject: [PATCH v2 0/2] mtd: fix use-after-free on unbind with open handles
Date: Fri, 9 Oct 2026 15:35:53 +0800 [thread overview]
Message-ID: <cover.1791512623.git.tze.yee.ng@altera.com> (raw)
From: Tze Yee Ng <tze.yee.ng@altera.com>
An open /dev/mtdX can outlive driver unbind. The MTD core keeps
mtd_info registered until the last close, but a spi-nor allocated
with devm_*() on the SPI device is already freed, so a later
close/ioctl/read hits freed memory.
v1 tried to fix that with a spi-nor-local kref and nor->removed.
That duplicated mtd->refcnt and still missed get_device() after
unbind, suspend/resume, and eraseregions. v2 puts the lifetime in
the MTD core instead.
- Patch 1: add optional mtd->_free() (called from kref release)
and mtd->removed so the core returns -ENODEV for hw ops, new
openers, and suspend/resume.
- Patch 2: on the spi-mem path, allocate spi_nor / params /
eraseregions / bouncebuf with kmalloc, install mtd->_free, and
set mtd->removed in remove() after draining in-flight ops.
Legacy controllers keep the old devres lifetime.
Changes in v2:
- Drop the unrelated RWW self-deadlock fix.
- New patch 1: MTD-core _free / removed hooks.
- Patch 2: drop the spi-nor kref / refcounted / controller_module
and the prep_and_lock*() removed checks; use the core hooks.
Also keep eraseregions on that lifetime, free on the probe
error path, and unregister debugfs from _free.
Tze Yee Ng (2):
mtd: core: add release hook and removed flag for unbind with open
handles
mtd: spi-nor: fix use-after-free on unbind with open handles
drivers/mtd/mtdcore.c | 20 ++++++++
drivers/mtd/spi-nor/core.c | 92 +++++++++++++++++++++++++++++------
drivers/mtd/spi-nor/core.h | 2 +
drivers/mtd/spi-nor/debugfs.c | 9 +---
include/linux/mtd/mtd.h | 13 +++++
5 files changed, 112 insertions(+), 24 deletions(-)
--
2.43.7
next reply other threads:[~2026-10-09 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 7:35 tze.yee.ng [this message]
2026-10-09 7:35 ` [PATCH v2 1/2] mtd: core: add release hook and removed flag for " tze.yee.ng
2026-10-09 7:49 ` sashiko-bot
2026-10-09 7:35 ` [PATCH v2 2/2] mtd: spi-nor: fix use-after-free on " tze.yee.ng
2026-10-09 7:57 ` sashiko-bot
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=cover.1791512623.git.tze.yee.ng@altera.com \
--to=tze.yee.ng@altera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=takahiro.kuwano@infineon.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®