linux-kernel - “KASAN: slab-out-of-bounds Read in squashfs_get_id” should have the same root cause with "KASAN: use-after-free Read in squashfs_get

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: <CAD-N9QUWaO0YFz1ORE4-vgGNnsJrgt50S0bPY2JcUPWaKA17Aw@mail.gmail.com>
Date:   Thu, 14 Jan 2021 08:58:02 +0800
From:   慕冬亮 <mudongliangabcd@...il.com>
To:     linux-kernel <linux-kernel@...r.kernel.org>,
        phillip@...ashfs.org.uk,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: “KASAN: slab-out-of-bounds Read in squashfs_get_id” should have the same root cause with "KASAN: use-after-free Read in squashfs_get_id"

Dear kernel developers,

I found that on the syzbot dashboard, “KASAN: slab-out-of-bounds Read
in squashfs_get_id”
(https://syzkaller.appspot.com/bug?id=16a7f16e9182bbfdbd2142306a82a41d4debb670)
and
"KASAN: use-after-free Read in squashfs_get_id"
(https://syzkaller.appspot.com/bug?id=eea996d785a0f2379bcfabaf7501329235a1f006)
should share the same root cause.

The reason for my above statement is that 1) their PoCs are exactly
the same as each other; 2) the stack traces are also the same;

If you can have any issues with this statement or our information is
useful to you, please let us know. Thanks very much.

--
My best regards to you.

     No System Is Safe!
     Dongliang Mu