linux-kernel - Re: [syzbot] [io-uring?] memory leak in iovec_from

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]

Message-ID: <9e600e62-499c-4f4f-a4fc-846bb0afb110@kernel.dk>
Date: Wed, 14 Jan 2026 09:09:48 -0700
From: Jens Axboe <axboe@...nel.dk>
To: syzbot <syzbot+df0b387708573ad096ce@...kaller.appspotmail.com>,
 io-uring@...r.kernel.org, linux-kernel@...r.kernel.org,
 syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [io-uring?] memory leak in iovec_from_user (4)

On 1/14/26 1:35 AM, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    b54345928fa1 Merge tag 'gfs2-for-6.19-rc6' of git://git.ke..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15f82052580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=87bc41cae23d2144
> dashboard link: https://syzkaller.appspot.com/bug?extid=df0b387708573ad096ce
> compiler:       gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=147ef99a580000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=109655fa580000
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/23b084ff7602/disk-b5434592.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/3ecd3b0e8e34/vmlinux-b5434592.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/b42ab3574030/bzImage-b5434592.xz

I still think these are false positives, and forcing another kmemleak scan
would make them go away. Which the syzbot reproducers should arguably just
do. As mentioned in the email from this week, I ran into various others
of these, all of them invalid. A rescan sorts it out.

#syz invalid

-- 
Jens Axboe