linux-kernel - Re: [PATCH] io_uring: fix memleak in io_sqe_files

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 10 Jul 2020 07:51:18 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Yang Yingliang <yangyingliang@...wei.com>,
        io-uring@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] io_uring: fix memleak in io_sqe_files_register()

On 7/10/20 8:14 AM, Yang Yingliang wrote:
> I got a memleak report when doing some fuzz test:
> 
> BUG: memory leak
> unreferenced object 0x607eeac06e78 (size 8):
>   comm "test", pid 295, jiffies 4294735835 (age 31.745s)
>   hex dump (first 8 bytes):
>     00 00 00 00 00 00 00 00                          ........
>   backtrace:
>     [<00000000932632e6>] percpu_ref_init+0x2a/0x1b0
>     [<0000000092ddb796>] __io_uring_register+0x111d/0x22a0
>     [<00000000eadd6c77>] __x64_sys_io_uring_register+0x17b/0x480
>     [<00000000591b89a6>] do_syscall_64+0x56/0xa0
>     [<00000000864a281d>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
> 
> 
> Call percpu_ref_exit() on error path to avoid
> refcount memleak.

Applied, thanks.

-- 
Jens Axboe