From: Chuck Lever <cel@kernel.org>
To: Benjamin Coddington <bcodding@hammerspace.com>,
bsdhenrymartin@gmail.com, Trond Myklebust <trondmy@kernel.org>
Cc: linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
Anna Schumaker <anna@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] sunrpc: fix TLS connect_worker rpc_clnt lifetime UAF
Date: Wed, 11 Mar 2026 10:20:45 -0400 [thread overview]
Message-ID: <19d1571d-0415-42ff-b9b4-8c866f566958@kernel.org> (raw)
In-Reply-To: <FEF1FBB7-B82A-4A71-8F25-689EB5CD8F41@hammerspace.com>
On 3/11/26 10:18 AM, Benjamin Coddington wrote:
> On 9 Mar 2026, at 7:19, bsdhenrymartin@gmail.com wrote:
>> @@ -2805,7 +2811,11 @@ static void xs_connect(struct rpc_xprt *xprt, struct rpc_task *task)
>> } else
>> dprintk("RPC: xs_connect scheduled xprt %p\n", xprt);
>>
>> - transport->clnt = task->tk_client;
>> + if (transport->connect_worker.work.func == xs_tcp_tls_setup_socket) {
>
> ^^ .. this seems a bit brittle..
This caught my eye as well.
>
>> + WARN_ON_ONCE(transport->clnt != NULL);
>> + refcount_inc(&task->tk_client->cl_count);
>> + transport->clnt = task->tk_client;
>> + }
>> queue_delayed_work(xprtiod_workqueue,
>> &transport->connect_worker,
>> delay);
>
> This fix works and I think its great for stable:
>
> Reviewed-by: Benjamin Coddington <bcodding@hammerspace.com>
>
> But I think we ended up with this problem because we're re-using the
> rpc_clnt in order to set up the lower_transport, and maybe we don't have to
> actually mix those layers.
>
> Chuck, Trond - can we use a "dummy" rpc_program to create the lower rpc_clnt,
> and keep the lifetime of the original rpc_clnt disconnected from the
> sock_xprt? I can send a patch..
The upper/lower architecture was Trond's suggestion. I just implemented
it (poorly). Let's see whatcha got!
--
Chuck Lever
prev parent reply other threads:[~2026-03-11 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 11:19 [PATCH] sunrpc: fix TLS connect_worker rpc_clnt lifetime UAF bsdhenrymartin
2026-03-09 14:45 ` Jeff Layton
2026-03-11 14:18 ` Benjamin Coddington
2026-03-11 14:20 ` Chuck Lever [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=19d1571d-0415-42ff-b9b4-8c866f566958@kernel.org \
--to=cel@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=anna@kernel.org \
--cc=bcodding@hammerspace.com \
--cc=bsdhenrymartin@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jlayton@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=netdev@vger.kernel.org \
--cc=okorniev@redhat.com \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tom@talpey.com \
--cc=trondmy@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