linux-ext4 - Re: [PATCH -v2] ext4: add more paranoia checking in ext4_expand_extra

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:   Mon, 18 Nov 2019 20:36:40 -0800
From:   Eric Biggers <ebiggers@...nel.org>
To:     "Theodore Y. Ts'o" <tytso@....edu>
Cc:     kbuild test robot <lkp@...el.com>, kbuild-all@...ts.01.org,
        Ext4 Developers List <linux-ext4@...r.kernel.org>,
        syzbot+f8d6f8386ceacdbfff57@...kaller.appspotmail.com,
        stable@...nel.org
Subject: Re: [PATCH -v2] ext4: add more paranoia checking in
 ext4_expand_extra_isize handling

On Mon, Nov 18, 2019 at 11:21:20PM -0500, Theodore Y. Ts'o wrote:
> On Mon, Nov 18, 2019 at 06:15:26PM -0800, Eric Biggers wrote:
> > Is this patch intended to address
> > https://lore.kernel.org/linux-ext4/000000000000950f21059564e4c7@google.com
> > as well?  If so, you can add the second Reported-by line so that both syzbot
> > reports get closed.
> 
> Yes, it appears to be the same issue.  Thanks for pointing this out!
> 
>      		      	       	       - Ted

There's actually a third that looks very similar too:

"KASAN: use-after-free Write in __ext4_expand_extra_isize (2)"
https://lkml.kernel.org/linux-ext4/0000000000000d74c7059564e17f@google.com/

If these are all fixed by this patch, you can use:

Reported-by: syzbot+f8d6f8386ceacdbfff57@...kaller.appspotmail.com
Reported-by: syzbot+33d7ea72e47de3bdf4e1@...kaller.appspotmail.com
Reported-by: syzbot+44b6763edfc17144296f@...kaller.appspotmail.com