All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: David Airlie <airlied@linux.ie>,
	kernel-janitors@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/dumb-buffers: Integer overflow in drm_mode_create_ioctl()
Date: Wed, 16 May 2018 15:41:50 +0000	[thread overview]
Message-ID: <20180516154150.iap2mm6h4rznod3n@mwanda> (raw)
In-Reply-To: <20180516151554.grlkemklosrksxpm@mwanda>

Btw, I've looked at this some more and I'm 99% sure there is no way to
exploit it.  The "if (PAGE_ALIGN(size) = 0)" prevents the integer
overflow in __vgem_gem_create() that I was worried about.

regards,
dan carpenter



WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: David Airlie <airlied@linux.ie>,
	kernel-janitors@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/dumb-buffers: Integer overflow in drm_mode_create_ioctl()
Date: Wed, 16 May 2018 18:41:50 +0300	[thread overview]
Message-ID: <20180516154150.iap2mm6h4rznod3n@mwanda> (raw)
In-Reply-To: <20180516151554.grlkemklosrksxpm@mwanda>

Btw, I've looked at this some more and I'm 99% sure there is no way to
exploit it.  The "if (PAGE_ALIGN(size) == 0)" prevents the integer
overflow in __vgem_gem_create() that I was worried about.

regards,
dan carpenter


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-05-16 15:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09  7:22 [PATCH] drm/dumb-buffers: Integer overflow in drm_mode_create_ioctl() Dan Carpenter
2018-05-09  7:22 ` Dan Carpenter
2018-05-09  8:12 ` [PATCH v2] " Dan Carpenter
2018-05-09  8:12   ` Dan Carpenter
2018-05-09  8:18   ` Chris Wilson
2018-05-09  8:18     ` Chris Wilson
2018-05-09 11:59     ` Dan Carpenter
2018-05-09 11:59       ` Dan Carpenter
2018-05-16 14:00     ` Dan Carpenter
2018-05-16 14:00       ` Dan Carpenter
2018-05-16 14:26       ` Chris Wilson
2018-05-16 14:26         ` Chris Wilson
2018-05-16 14:52         ` Dan Carpenter
2018-05-16 14:52           ` Dan Carpenter
2018-05-16 14:56           ` Chris Wilson
2018-05-16 15:15             ` Dan Carpenter
2018-05-16 15:15               ` Dan Carpenter
2018-05-16 15:25               ` Chris Wilson
2018-05-16 15:41               ` Dan Carpenter [this message]
2018-05-16 15:41                 ` Dan Carpenter
2018-05-16 15:57       ` Daniel Vetter
2018-05-16 15:57         ` Daniel Vetter
2018-05-09  8:23 ` [PATCH] " Daniel Vetter
2018-05-09  8:23   ` Daniel Vetter

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=20180516154150.iap2mm6h4rznod3n@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=airlied@linux.ie \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-janitors@vger.kernel.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 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.