From: Deepanshu Kartikey <kartikey406@gmail.com>
To: jgg@ziepe.ca, leon@kernel.org
Cc: hemanth.selam@gmail.com, yishaih@nvidia.com, edwards@nvidia.com,
mrgolin@amazon.com, michael.j.ruhl@intel.com,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
Deepanshu Kartikey <kartikey406@gmail.com>,
syzbot+d60be66dd00b4490fa96@syzkaller.appspotmail.com
Subject: [PATCH] RDMA/uverbs: Fix radix tree node leak in uapi_add_elm()
Date: Fri, 6 Nov 2026 07:09:08 +0530 [thread overview]
Message-ID: <20261106013908.21789-1-kartikey406@gmail.com> (raw)
syzbot reported a memory leak of radix_tree_node objects allocated
while registering a siw device:
unreferenced object 0xffff88810d78f488 (size 576):
radix_tree_node_alloc+0x81/0x1a0 lib/radix-tree.c:276
radix_tree_insert+0x140/0x390 lib/radix-tree.c:712
uapi_add_elm+0x61/0x140 drivers/infiniband/core/uverbs_uapi.c:41
uverbs_alloc_api+0x85/0xc50 drivers/infiniband/core/uverbs_uapi.c:659
ib_uverbs_add_one+0x1b1/0x350 drivers/infiniband/core/uverbs_main.c:1196
ib_register_device+0x4fe/0x7f0 drivers/infiniband/core/device.c:1503
siw_newlink+0x36a/0x3f0 drivers/infiniband/sw/siw/siw_main.c:433
radix_tree_insert() can fail with -ENOMEM after __radix_tree_create()
has already linked intermediate nodes into the tree, leaving them with
no entries. uapi_add_elm() frees the element on failure, but nothing
frees these empty nodes: uverbs_destroy_api() only removes populated
slots, and radix tree nodes are freed only as a side effect of
deleting an entry. The nodes are therefore leaked when the uapi is
destroyed.
On -ENOMEM, populate the same key with a dummy entry and delete it
again so that radix_tree_delete() reclaims the empty node chain.
Reported-by: syzbot+d60be66dd00b4490fa96@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=d60be66dd00b4490fa96
Tested-by: syzbot+d60be66dd00b4490fa96@syzkaller.appspotmail.com
Fixes: 9ed3e5f44772 ("IB/uverbs: Build the specs into a radix tree at runtime")
Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
---
drivers/infiniband/core/uverbs_uapi.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/drivers/infiniband/core/uverbs_uapi.c b/drivers/infiniband/core/uverbs_uapi.c
index b67db3790f03..6b2eb392b076 100644
--- a/drivers/infiniband/core/uverbs_uapi.c
+++ b/drivers/infiniband/core/uverbs_uapi.c
@@ -15,6 +15,7 @@ static int ib_uverbs_notsupp(struct uverbs_attr_bundle *attrs)
static void *uapi_add_elm(struct uverbs_api *uapi, u32 key, size_t alloc_size)
{
+ static void *dummy;
void *elm;
int rc;
@@ -27,6 +28,16 @@ static void *uapi_add_elm(struct uverbs_api *uapi, u32 key, size_t alloc_size)
rc = radix_tree_insert(&uapi->radix, key, elm);
if (rc) {
kfree(elm);
+
+ /*
+ * A failed radix_tree_insert() can leave empty intermediate
+ * nodes linked in the tree. They are only freed when an entry
+ * under them is deleted, so populate and delete the slot to
+ * reclaim them.
+ */
+ if (rc == -ENOMEM &&
+ !radix_tree_insert(&uapi->radix, key, &dummy))
+ radix_tree_delete(&uapi->radix, key);
return ERR_PTR(rc);
}
--
2.43.0
reply other threads:[~2026-11-06 1:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261106013908.21789-1-kartikey406@gmail.com \
--to=kartikey406@gmail.com \
--cc=edwards@nvidia.com \
--cc=hemanth.selam@gmail.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=michael.j.ruhl@intel.com \
--cc=mrgolin@amazon.com \
--cc=syzbot+d60be66dd00b4490fa96@syzkaller.appspotmail.com \
--cc=yishaih@nvidia.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
all inboxes | Powered by JetHome®