From: "Jan Beulich" <JBeulich@suse.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Cc: xen-devel <xen-devel@lists.xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
virtualization@lists.linux-foundation.org
Subject: Re: [Xen-devel] potential integer overflow in xenbus_file_write()
Date: Tue, 16 Oct 2012 09:54:23 +0100 [thread overview]
Message-ID: <507D3CDF02000078000A1A11@nat28.tlf.novell.com> (raw)
In-Reply-To: <1350296757.18058.21.camel@zakaz.uk.xensource.com>
>>> On 15.10.12 at 12:25, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Thu, 2012-09-13 at 19:00 +0300, Dan Carpenter wrote:
>> Hi,
>
> Thanks Dan. I'm not sure anyone from Xen-land really monitors
> virtualization@. Adding xen-devel and Konrad.
>
>>
>> I was reading some code and had a question in xenbus_file_write()
>>
>> drivers/xen/xenbus/xenbus_dev_frontend.c
>> 461 if ((len + u->len) > sizeof(u->u.buffer)) {
>> ^^^^^^^^^^^^
>> Can this addition overflow?
>
> len is a size_t and u->len is an unsigned int, so I expect so.
>
>> Should the test be something like:
>>
>> if (len > sizeof(u->u.buffer) || len + u->len > sizeof(u->u.buffer)) {
>
> I think that would do it.
Actually, it can remain a single range check:
if (len > sizeof(u->u.buffer) - u->len) {
because the rest of the code guarantees u->len to be less or
equal to sizeof(u->u.buffer) at all times.
Jan
prev parent reply other threads:[~2012-10-16 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 16:00 potential integer overflow in xenbus_file_write() Dan Carpenter
2012-10-15 10:25 ` Ian Campbell
[not found] ` <1350296757.18058.21.camel@zakaz.uk.xensource.com>
2012-10-16 8:54 ` Jan Beulich [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=507D3CDF02000078000A1A11@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Campbell@citrix.com \
--cc=dan.carpenter@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xen.org \
/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