linux-kernel - Re: [PATCH] usb: usbtmc: initialize memory written to device

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOV59eW1fyQYZWQO9+GvEamFPPo5DH=beM2P1eZ2x7zgwsX_iw@mail.gmail.com>
Date: Fri, 4 Oct 2024 15:38:56 +0200
From: Ⲡⲟⲓⲙⲏⲛ <bemenboshra2001@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Pimyn@....codeaurora.org, Girgis@....codeaurora.org, 
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com, nogikh@...gle.com, glider@...gle.com, 
	dvyukov@...gle.com, elver@...gle.com, pimyn@...gle.com, 
	syzbot+8f282cce71948071c335@...kaller.appspotmail.com
Subject: Re: [PATCH] usb: usbtmc: initialize memory written to device

On Fri, 4 Oct 2024 at 14:58, Greg KH <gregkh@...uxfoundation.org> wrote:

> Why "explicit"?
Thank you. I think we could use memzero here instead.
> Also, what about commit 625fa77151f0 ("USB: usbtmc: prevent
> kernel-usb-infoleak"), doesn't that solve the issue here?
You're right. This commit is not in 6.11, so I missed it.