From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Tomas Bortoli <tomasbortoli@gmail.com>,
wg@grandegger.com, linux-can@vger.kernel.org
Cc: davem@davemloft.net, gregkh@linuxfoundation.org,
alexios.zavras@intel.com, tglx@linutronix.de,
allison@lohutok.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller@googlegroups.com
Subject: Re: [PATCH] peak_usb: Fix info-leaks to USB devices
Date: Fri, 2 Aug 2019 13:45:59 +0200 [thread overview]
Message-ID: <94a82ee7-880e-704c-14ea-328b17854441@pengutronix.de> (raw)
In-Reply-To: <20190731145447.29270-1-tomasbortoli@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 766 bytes --]
On 7/31/19 4:54 PM, Tomas Bortoli wrote:
> Uninitialized Kernel memory can leak to USB devices.
>
> Fix by using kzalloc() instead of kmalloc() on the affected buffers.
>
> Signed-off-by: Tomas Bortoli <tomasbortoli@gmail.com>
> Reported-by: syzbot+d6a5a1a3657b596ef132@syzkaller.appspotmail.com
> Reported-by: syzbot+513e4d0985298538bf9b@syzkaller.appspotmail.com
Applied, but split into two patches, as the problem was introduced in
two separate commits.
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-08-02 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 14:54 [PATCH] peak_usb: Fix info-leaks to USB devices Tomas Bortoli
2019-08-02 11:45 ` Marc Kleine-Budde [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94a82ee7-880e-704c-14ea-328b17854441@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tomasbortoli@gmail.com \
--cc=wg@grandegger.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).