From: "Jérémy Jean" <Jeremy.Jean@oss.cyber.gouv.fr>
To: Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
Dominique Martinet <asmadeus@codewreck.org>
Cc: "Christian Schoenebeck" <linux_oss@crudebyte.com>,
v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
"Jérémy Jean" <Jeremy.Jean@oss.cyber.gouv.fr>,
stable@kernel.org
Subject: [PATCH] 9p: pin request under client lock in p9_tag_lookup
Date: Wed, 30 Sep 2026 20:13:58 +0000 [thread overview]
Message-ID: <20260930201357.590469-2-Jeremy.Jean@oss.cyber.gouv.fr> (raw)
9P clients keep separate request tables but share one request cache.
p9_tag_lookup() can race with the final p9_req_put() and pin a request
reused by another client. Both clients can then complete it, freeing
its response while the caller still parses it, creating a UAF that
KASAN reports as:
BUG: KASAN: slab-use-after-free in p9pdu_readf+0x362/0x2130
Read of size 4 at addr ffff888009520000 by task repro/82
Freed by task 50:
p9_req_put+0x1a4/0x1f0
p9_read_work+0x916/0xf80
Hold the client lock while finding and pinning the request, preventing
removal and reuse between these operations.
Fixes: 728356dedeff ("9p: Add refcount to p9_req_t")
Cc: stable@kernel.org
Assisted-by: LLM
Signed-off-by: Jérémy Jean <Jeremy.Jean@oss.cyber.gouv.fr>
---
net/9p/client.c | 26 ++++++++++----------------
1 file changed, 10 insertions(+), 16 deletions(-)
diff --git a/net/9p/client.c b/net/9p/client.c
index ef64546c6d52..fd72f05128d1 100644
--- a/net/9p/client.c
+++ b/net/9p/client.c
@@ -235,24 +235,18 @@ p9_tag_alloc(struct p9_client *c, int8_t type, uint t_size, uint r_size,
struct p9_req_t *p9_tag_lookup(struct p9_client *c, u16 tag)
{
struct p9_req_t *req;
+ unsigned long flags;
- rcu_read_lock();
-again:
+ /*
+ * Pin the request while removal from this client's IDR is excluded.
+ * Tag equality alone cannot distinguish a request recycled for another
+ * client from the same SLAB_TYPESAFE_BY_RCU cache.
+ */
+ spin_lock_irqsave(&c->lock, flags);
req = idr_find(&c->reqs, tag);
- if (req) {
- /* We have to be careful with the req found under rcu_read_lock
- * Thanks to SLAB_TYPESAFE_BY_RCU we can safely try to get the
- * ref again without corrupting other data, then check again
- * that the tag matches once we have the ref
- */
- if (!p9_req_try_get(req))
- goto again;
- if (req->tc.tag != tag) {
- p9_req_put(c, req);
- goto again;
- }
- }
- rcu_read_unlock();
+ if (req && !p9_req_try_get(req))
+ req = NULL;
+ spin_unlock_irqrestore(&c->lock, flags);
return req;
}
--
2.47.3
next reply other threads:[~2026-09-30 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 20:13 Jérémy Jean [this message]
2026-10-29 5:50 ` Dominique Martinet
2026-10-29 10:56 ` Jérémy Jean
2026-10-29 13:30 ` Dominique Martinet
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=20260930201357.590469-2-Jeremy.Jean@oss.cyber.gouv.fr \
--to=jeremy.jean@oss.cyber.gouv.fr \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=stable@kernel.org \
--cc=v9fs@lists.linux.dev \
/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®