[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <176667533028.68806.11770987520631890583.b4-ty@kernel.dk>
Date: Thu, 25 Dec 2025 08:08:50 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Prithvi Tambewagh <activprithvi@...il.com>
Cc: io-uring@...r.kernel.org, brauner@...nel.org, jack@...e.cz,
viro@...iv.linux.org.uk, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kernel-mentees@...ts.linux.dev,
skhan@...uxfoundation.org, david.hunter.linux@...il.com, khalid@...nel.org,
syzbot+00e61c43eb5e4740438f@...kaller.appspotmail.com,
stable@...r.kernel.org
Subject: Re: [PATCH v2] io_uring: fix filename leak in __io_openat_prep()
On Thu, 25 Dec 2025 12:58:29 +0530, Prithvi Tambewagh wrote:
> __io_openat_prep() allocates a struct filename using getname(). However,
> for the condition of the file being installed in the fixed file table as
> well as having O_CLOEXEC flag set, the function returns early. At that
> point, the request doesn't have REQ_F_NEED_CLEANUP flag set. Due to this,
> the memory for the newly allocated struct filename is not cleaned up,
> causing a memory leak.
>
> [...]
Applied, thanks!
[1/1] io_uring: fix filename leak in __io_openat_prep()
commit: b14fad555302a2104948feaff70503b64c80ac01
Best regards,
--
Jens Axboe
Powered by blists - more mailing lists