From: syzbot <syzbot+b2cfdac9ae5278d4b621@syzkaller.appspotmail.com>
To: nightu.pwn@gmail.com
Cc: nightu.pwn@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [squashfs?] VFS: Close: file count is zero (use-after-free)
Date: Sun, 02 Jun 2024 23:10:10 -0700 [thread overview]
Message-ID: <0000000000008f57d70619f62fe8@google.com> (raw)
In-Reply-To: <CAN-2BNQfJF3b-Li56Nu13JxHKu3oMSetiPiEWzYa=HzSAAdkHQ@mail.gmail.com>
> please test file uaf in udmabuf_create
>
> #syz test https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
want either no args or 2 args (repo, branch), got 1
> 0e1980c40b6e
> ---
> drivers/dma-buf/udmabuf.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/dma-buf/udmabuf.c b/drivers/dma-buf/udmabuf.c
> index afa8bfd2a2a9..53035c601e92 100644
> --- a/drivers/dma-buf/udmabuf.c
> +++ b/drivers/dma-buf/udmabuf.c
> @@ -382,6 +382,7 @@ static long udmabuf_create(struct miscdevice *device,
>
> kfree(folios);
> fput(memfd);
> + memfd = NULL;
> }
>
> flags = head->flags & UDMABUF_FLAGS_CLOEXEC ? O_CLOEXEC : 0;
> --
next parent reply other threads:[~2024-06-03 6:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAN-2BNQfJF3b-Li56Nu13JxHKu3oMSetiPiEWzYa=HzSAAdkHQ@mail.gmail.com>
2024-06-03 6:10 ` syzbot [this message]
[not found] <CAN-2BNRG3qMSVgBm=6jD3tv=nDAzByebEJF8k2UWUdo=vAEeSw@mail.gmail.com>
2024-06-03 6:40 ` [syzbot] [squashfs?] VFS: Close: file count is zero (use-after-free) syzbot
[not found] <CAN-2BNRaHxnr5_nJ8eu1h2uBYOFnSsRJF=dpvscvO7H=b+mX-Q@mail.gmail.com>
2024-06-03 6:10 ` syzbot
[not found] <CAN-2BNQVPdaPb-LryqBLti2EEEm5Svgi559wGeuHN0MO6rr3fg@mail.gmail.com>
2024-06-03 6:08 ` syzbot
[not found] <CAN-2BNR=xVQKPU4k4EbP5o5oxW3g2Rj2AwaDBrAZ+wuoNWbpWQ@mail.gmail.com>
2024-06-03 5:49 ` syzbot
2024-06-02 15:20 syzbot
2024-06-13 6:23 ` Kasireddy, Vivek
2024-06-13 7:10 ` 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=0000000000008f57d70619f62fe8@google.com \
--to=syzbot+b2cfdac9ae5278d4b621@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nightu.pwn@gmail.com \
--cc=syzkaller-bugs@googlegroups.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