From: Ira Weiny <ira.weiny@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dingisoul <dingiso.kernel@gmail.com>,
Dave Jiang <dave.jiang@intel.com>, <nvdimm@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: [GIT PULL] NVDIMM fixes for 7.0-rc5
Date: Tue, 17 Mar 2026 15:59:30 -0500 [thread overview]
Message-ID: <69b9c0b276c61_290b1007c@iweiny-mobl.notmuch> (raw)
Hey Linus, please pull from:
https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git tags/libnvdimm-fixes-7.0-rc5
... to get a fix for a potential older bug recently discovered.
It is a use after free which requires a memory allocation which is probably why
it was not seen without an analysis tool.
This has been in next for a week without issues.
Thank you,
Ira
---
The following changes since commit 1f318b96cc84d7c2ab792fcc0bfd42a7ca890681:
Linux 7.0-rc3 (2026-03-08 16:56:54 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git tags/libnvdimm-fixes-7.0-rc5
for you to fetch changes up to a8aec14230322ed8f1e8042b6d656c1631d41163:
nvdimm/bus: Fix potential use after free in asynchronous initialization (2026-03-09 09:38:22 -0500)
----------------------------------------------------------------
libnvdimm fixes for 7.0-rc5
- Fix old potential use after free bug
----------------------------------------------------------------
Ira Weiny (1):
nvdimm/bus: Fix potential use after free in asynchronous initialization
drivers/nvdimm/bus.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
next reply other threads:[~2026-03-17 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 20:59 Ira Weiny [this message]
2026-03-17 23:59 ` pr-tracker-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=69b9c0b276c61_290b1007c@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=dave.jiang@intel.com \
--cc=dingiso.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=torvalds@linux-foundation.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 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®