linux-ext4 - Re: kernel BUG in ext4_free

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>] [day] [month] [year] [list]

Message-ID: <0000000000005555f005f3a2d3da@google.com>
Date:   Wed, 01 Feb 2023 04:45:39 -0800
From:   syzbot <syzbot+15cd994e273307bf5cfa@...kaller.appspotmail.com>
To:     adilger.kernel@...ger.ca, gregkh@...uxfoundation.org,
        joneslee@...gle.com, lczerner@...hat.com, lee@...nel.org,
        linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
        nogikh@...gle.com, sashal@...nel.org, stable@...r.kernel.org,
        syzkaller-android-bugs@...glegroups.com, tadeusz.struk@...aro.org,
        tudor.ambarus@...aro.org, tytso@....edu
Subject: Re: kernel BUG in ext4_free_blocks (2)

This bug is marked as fixed by commit:
ext4: block range must be validated before use in ext4_mb_clear_bb()

But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:

#syz fix: exact-commit-title

Until then the bug is still considered open and new crashes with
the same signature are ignored.

Kernel: Android 5.10
Dashboard link: https://syzkaller.appspot.com/bug?extid=15cd994e273307bf5cfa

---
[1] I expect the commit to be present in:

1. android12-5.10-lts branch of
https://android.googlesource.com/kernel/common