From: Dave Jiang <dave.jiang@intel.com>
To: Ira Weiny <ira.weiny@intel.com>,
nvdimm@lists.linux.dev, Dan Williams <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Dingisoul <dingiso.kernel@gmail.com>
Subject: Re: [PATCH] nvdimm/bus: Fix potential use after free in asynchronous initialization
Date: Fri, 6 Mar 2026 16:07:11 -0700 [thread overview]
Message-ID: <18b6665b-2964-423c-8ba2-b7df28b95d62@intel.com> (raw)
In-Reply-To: <20260306-fix-uaf-async-init-v1-1-a28fd7526723@intel.com>
On 3/6/26 11:33 AM, Ira Weiny wrote:
> Dingisoul with KASAN reports a use after free if device_add() fails in
> nd_async_device_register().
>
> Commit b6eae0f61db2 ("libnvdimm: Hold reference on parent while
> scheduling async init") correctly added a reference on the parent device
> to be held until asynchronous initialization was complete. However, if
> device_add() results in an allocation failure the ref count of the
> device drops to 0 prior to the parent pointer being accessed. Thus
> resulting in use after free.
>
> The bug bot AI correctly identified the fix. Save a reference to the
> parent pointer to be used to drop the parent reference regardless of the
> outcome of device_add().
>
> Reported-by: Dingisoul <dingiso.kernel@gmail.com>
> Closes: http://lore.kernel.org/8855544b-be9e-4153-aa55-0bc328b13733@gmail.com
> Fixes: b6eae0f61db2 ("libnvdimm: Hold reference on parent while scheduling async init")
> Cc: stable@vger.kernel.org
> Signed-off-by: Ira Weiny <ira.weiny@intel.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/nvdimm/bus.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/nvdimm/bus.c b/drivers/nvdimm/bus.c
> index bd9621d3f73c..45b7d756e39a 100644
> --- a/drivers/nvdimm/bus.c
> +++ b/drivers/nvdimm/bus.c
> @@ -486,14 +486,15 @@ EXPORT_SYMBOL_GPL(nd_synchronize);
> static void nd_async_device_register(void *d, async_cookie_t cookie)
> {
> struct device *dev = d;
> + struct device *parent = dev->parent;
>
> if (device_add(dev) != 0) {
> dev_err(dev, "%s: failed\n", __func__);
> put_device(dev);
> }
> put_device(dev);
> - if (dev->parent)
> - put_device(dev->parent);
> + if (parent)
> + put_device(parent);
> }
>
> static void nd_async_device_unregister(void *d, async_cookie_t cookie)
>
> ---
> base-commit: c107785c7e8dbabd1c18301a1c362544b5786282
> change-id: 20260306-fix-uaf-async-init-3697998d8faf
>
> Best regards,
> --
> Ira Weiny <ira.weiny@intel.com>
>
prev parent reply other threads:[~2026-03-06 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 18:33 [PATCH] nvdimm/bus: Fix potential use after free in asynchronous initialization Ira Weiny
2026-03-06 23:07 ` Dave Jiang [this message]
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=18b6665b-2964-423c-8ba2-b7df28b95d62@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dingiso.kernel@gmail.com \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=vishal.l.verma@intel.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