From: Keith Busch <kbusch@kernel.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org,
Dmitry Bogdanov <d.bogdanov@yadro.com>,
stable@vger.kernel.org, Guangwu Zhang <guazhang@redhat.com>
Subject: Re: [PATCH] nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference
Date: Wed, 21 Jan 2026 08:21:48 -0700 [thread overview]
Message-ID: <aXDvDHaAU8cUGlZf@kbusch-mbp> (raw)
In-Reply-To: <20260121093854.1705806-1-ming.lei@redhat.com>
On Wed, Jan 21, 2026 at 05:38:54PM +0800, Ming Lei wrote:
> There is a race condition in nvmet_bio_done() that can cause a NULL
> pointer dereference in blk_cgroup_bio_start():
>
> 1. nvmet_bio_done() is called when a bio completes
> 2. nvmet_req_complete() is called, which invokes req->ops->queue_response(req)
> 3. The queue_response callback can re-queue and re-submit the same request
> 4. The re-submission reuses the same inline_bio from nvmet_req
> 5. Meanwhile, nvmet_req_bio_put() (called after nvmet_req_complete)
> invokes bio_uninit() for inline_bio, which sets bio->bi_blkg to NULL
> 6. The re-submitted bio enters submit_bio_noacct_nocheck()
> 7. blk_cgroup_bio_start() dereferences bio->bi_blkg, causing a crash:
>
> BUG: kernel NULL pointer dereference, address: 0000000000000028
> #PF: supervisor read access in kernel mode
> RIP: 0010:blk_cgroup_bio_start+0x10/0xd0
> Call Trace:
> submit_bio_noacct_nocheck+0x44/0x250
> nvmet_bdev_execute_rw+0x254/0x370 [nvmet]
> process_one_work+0x193/0x3c0
> worker_thread+0x281/0x3a0
>
> Fix this by reordering nvmet_bio_done() to call nvmet_req_bio_put()
> BEFORE nvmet_req_complete(). This ensures the bio is cleaned up before
> the request can be re-submitted, preventing the race condition.
Thanks, applied to nvme-6.19.
prev parent reply other threads:[~2026-01-21 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 9:38 [PATCH] nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference Ming Lei
2026-01-21 10:14 ` Christoph Hellwig
2026-01-21 15:21 ` Keith Busch [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=aXDvDHaAU8cUGlZf@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=d.bogdanov@yadro.com \
--cc=guazhang@redhat.com \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.lei@redhat.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox