From: Clemens Ladisch <clemens@ladisch.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] firewire: cdev: check write quadlet request length to avoid buffer overflow
Date: Wed, 07 Jul 2010 13:55:48 +0200 [thread overview]
Message-ID: <4C346B44.2020407@ladisch.de> (raw)
In-Reply-To: <tkrat.b2582c62a3eaf0ab@s5r6.in-berlin.de>
Stefan Richter wrote:
> [...] Thus the only problem is that a bogus write quadlet
> request with user-specified length of < 3 will put 1...4 random bytes
> into the packet payload. But this is the user's problem then, not the
> kernel's.
But not being initialized, these are the kernel's bytes that get
disclosed.
Regards,
Clemens
next prev parent reply other threads:[~2010-07-07 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C29C1CA.1050705@ladisch.de>
2010-07-07 8:46 ` [PATCH] firewire: cdev: check write quadlet request length to avoid buffer overflow Stefan Richter
2010-07-07 9:50 ` [PATCH v2] " Stefan Richter
2010-07-07 10:01 ` [PATCH v3] " Stefan Richter
2010-07-07 11:55 ` Clemens Ladisch [this message]
2010-07-07 12:20 ` Stefan Richter
2010-07-07 12:37 ` [PATCH v4] " Stefan Richter
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=4C346B44.2020407@ladisch.de \
--to=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.