netdev - KASAN: use-after-free Read in ath9k_hif_usb_rx_cb (2) should share the same root cause with "KASAN: slab-out-of-bounds Read in ath9k_hif_usb_rx

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-N9QUvu8D0qbdy6HqKfVF2Lu2Z+e7Huf_vpHumE=dhqfUGgw@mail.gmail.com>
Date:   Wed, 13 Jan 2021 19:47:31 +0800
From:   慕冬亮 <mudongliangabcd@...il.com>
To:     ath9k-devel@....qualcomm.com, davem@...emloft.net, kuba@...nel.org,
        kvalo@...eaurora.org, linux-kernel <linux-kernel@...r.kernel.org>,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: KASAN: use-after-free Read in ath9k_hif_usb_rx_cb (2) should share
 the same root cause with "KASAN: slab-out-of-bounds Read in
 ath9k_hif_usb_rx_cb (2)"

Dear kernel developers,

I found that KASAN: use-after-free Read in ath9k_hif_usb_rx_cb (2) and
"KASAN: slab-out-of-bounds Read in ath9k_hif_usb_rx_cb (2)" should
share the same root cause.

The reasons for my above statement,  1) the stack trace is the same;
2) we observed two crash behaviors appear alternatively when you run
one PoC in its building environment multiple times. 3) their PoCs have
a really high similarity

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

--
My best regards to you.

     No System Is Safe!
     Dongliang Mu