[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b8606599-22ce-85af-21df-0a1c4a8f174b@hartkopp.net>
Date: Tue, 12 Jan 2021 10:12:02 +0100
From: Oliver Hartkopp <socketcan@...tkopp.net>
To: Cong Wang <xiyou.wangcong@...il.com>,
Jakub Kicinski <kuba@...nel.org>
Cc: syzbot <syzbot+057884e2f453e8afebc8@...kaller.appspotmail.com>,
Robin van der Gracht <robin@...tonic.nl>,
Oleksij Rempel <o.rempel@...gutronix.de>,
Marc Kleine-Budde <mkl@...gutronix.de>,
linux-can@...r.kernel.org, David Miller <davem@...emloft.net>,
Alexander Potapenko <glider@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: KMSAN: kernel-infoleak in move_addr_to_user (4)
On 12.01.21 01:17, Cong Wang wrote:
> On Mon, Jan 11, 2021 at 11:33 AM Jakub Kicinski <kuba@...nel.org> wrote:
>>
>> Looks like a AF_CAN socket:
>>
>> r0 = socket(0x1d, 0x2, 0x6)
>> getsockname$packet(r0, &(0x7f0000000100)={0x11, 0x0, 0x0, 0x1, 0x0, 0x6, @broadcast}, &(0x7f0000000000)=0x14)
>>
>
> Right, it seems we need a memset(0) in isotp_getname().
Yes m(
Sent a patch to fix it:
https://lore.kernel.org/linux-can/20210112090457.11262-1-socketcan@hartkopp.net/T/#u
Many thanks!
Oliver
Powered by blists - more mailing lists