Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
	Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] nvme-tcp: fix possible UAF in nvme_tcp_poll
Date: Mon, 24 Feb 2025 17:12:53 -0700	[thread overview]
Message-ID: <Z70LBUOpAbSSKuK9@kbusch-mbp> (raw)
In-Reply-To: <20250220111830.3185561-1-sagi@grimberg.me>

On Thu, Feb 20, 2025 at 01:18:30PM +0200, Sagi Grimberg wrote:
> nvme_tcp_poll() may race with the send path error handler because
> it may complete the request while it is actively being polled for
> completion, resulting in a UAF panic [1]:

Thanks, applied to nvme-6.14.


  parent reply	other threads:[~2025-02-25  0:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 11:18 [PATCH] nvme-tcp: fix possible UAF in nvme_tcp_poll Sagi Grimberg
2025-02-24 22:23 ` Chaitanya Kulkarni
2025-02-25  0:12 ` Keith Busch [this message]
2025-02-26  9:46 ` Hannes Reinecke

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=Z70LBUOpAbSSKuK9@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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