From: Prithvi Tambewagh <activprithvi@gmail.com>
To: syzbot+00e61c43eb5e4740438f@syzkaller.appspotmail.com,
brauner@kernel.org, jack@suse.cz, viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
Prithvi Tambewagh <activprithvi@gmail.com>
Subject: [PATCH] io_uring: Fix filename leak in __io_openat_prep
Date: Wed, 24 Dec 2025 20:07:48 +0530 [thread overview]
Message-ID: <20251224143748.45491-1-activprithvi@gmail.com> (raw)
In-Reply-To: <694bcb49.050a0220.35954c.001a.GAE@google.com>
#syz test git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git b927546677c876e26eba308550207c2ddf812a43
Signed-off-by: Prithvi Tambewagh <activprithvi@gmail.com>
---
io_uring/openclose.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/io_uring/openclose.c b/io_uring/openclose.c
index bfeb91b31bba..fc190a3d8112 100644
--- a/io_uring/openclose.c
+++ b/io_uring/openclose.c
@@ -75,8 +75,11 @@ static int __io_openat_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe
}
open->file_slot = READ_ONCE(sqe->file_index);
- if (open->file_slot && (open->how.flags & O_CLOEXEC))
+ if (open->file_slot && (open->how.flags & O_CLOEXEC)) {
+ putname(open->filename);
+ open->filename = NULL;
return -EINVAL;
+ }
open->nofile = rlimit(RLIMIT_NOFILE);
req->flags |= REQ_F_NEED_CLEANUP;
base-commit: b927546677c876e26eba308550207c2ddf812a43
--
2.34.1
next prev parent reply other threads:[~2025-12-24 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 11:15 [syzbot] [fs?] memory leak in getname_flags syzbot
2025-12-24 14:37 ` Prithvi Tambewagh [this message]
2025-12-24 15:07 ` syzbot
2025-12-25 6:34 ` Syzbot test for v2: io_uring: fix filename leak in __io_openat_prep() Prithvi Tambewagh
2025-12-25 7:03 ` [syzbot] [fs?] memory leak in getname_flags syzbot
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=20251224143748.45491-1-activprithvi@gmail.com \
--to=activprithvi@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+00e61c43eb5e4740438f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.