[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18bdd6d7d1e.f8bd3007064.1218727710101871071@siddh.me>
Date: Fri, 17 Nov 2023 18:47:02 +0530
From: Siddh Raman Pant <code@...dh.me>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@...aro.org>
Cc: "davem" <davem@...emloft.net>, "edumazet" <edumazet@...gle.com>,
"kuba" <kuba@...nel.org>, "pabeni" <pabeni@...hat.com>,
"linux-kernel" <linux-kernel@...r.kernel.org>,
"netdev" <netdev@...r.kernel.org>,
"syzkaller-bugs" <syzkaller-bugs@...glegroups.com>,
"syzbot+bbe84a4010eeea00982d"
<syzbot+bbe84a4010eeea00982d@...kaller.appspotmail.com>
Subject: Re: [syzbot] [net?] [nfc?] KASAN: slab-use-after-free Read in
nfc_alloc_send_skb
On Fri, 17 Nov 2023 18:18:56 +0530, Krzysztof Kozlowski wrote:
> Any checks would need to have proper locking. Or at least barriers...
> Adding checks without locks usually does not solve race conditions.
Yes of course. I just wanted to put whatever I tested out there.
> Other start is proper ref counting, so the structures are not released
> too early. We have several bugs like this in NFC before, so you can take
> a look at their fixes.
Sure.
Thanks,
Siddh
Powered by blists - more mailing lists