Re: KMSAN: kernel-infoleak in move_addr_to_user (4)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Jakub Kicinski <kuba@xxxxxxxxxx>
Subject: Re: KMSAN: kernel-infoleak in move_addr_to_user (4)
From: Cong Wang <xiyou.wangcong@xxxxxxxxx>
Date: Mon, 11 Jan 2021 16:17:03 -0800
Cc: syzbot <syzbot+057884e2f453e8afebc8@xxxxxxxxxxxxxxxxxxxxxxxxx>, Robin van der Gracht <robin@xxxxxxxxxxx>, Oleksij Rempel <o.rempel@xxxxxxxxxxxxxx>, Marc Kleine-Budde <mkl@xxxxxxxxxxxxxx>, linux-can@xxxxxxxxxxxxxxx, David Miller <davem@xxxxxxxxxxxxx>, Alexander Potapenko <glider@xxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Linux Kernel Network Developers <netdev@xxxxxxxxxxxxxxx>, syzkaller-bugs <syzkaller-bugs@xxxxxxxxxxxxxxxx>
In-reply-to: <20210111113059.42de599d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
References: <00000000000019908405b8891f9d@google.com> <20210111113059.42de599d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Mon, Jan 11, 2021 at 11:33 AM Jakub Kicinski <kuba@xxxxxxxxxx> 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().

Thanks.

Follow-Ups:
- Re: KMSAN: kernel-infoleak in move_addr_to_user (4)
  - From: Oliver Hartkopp

References:
- Re: KMSAN: kernel-infoleak in move_addr_to_user (4)
  - From: Jakub Kicinski

Prev by Date: Re: KMSAN: kernel-infoleak in move_addr_to_user (4)
Next by Date: Re: [PATCH v3 1/1] can: dev: add software tx timestamps
Previous by thread: Re: KMSAN: kernel-infoleak in move_addr_to_user (4)
Next by thread: Re: KMSAN: kernel-infoleak in move_addr_to_user (4)
Index(es):
- Date
- Thread

[Index of Archives] [Automotive Discussions] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API] [CAN Bus]