public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Vasiliy Kulikov <segoon@openwall.com>, David Airlie <airlied@linux.ie>
Cc: linux-kernel@vger.kernel.org, security@kernel.org
Subject: Re: [PATCH] char: agp: fix OOM and buffer overflow
Date: Tue, 19 Apr 2011 09:21:57 -0700	[thread overview]
Message-ID: <20110419162157.GD23196@kroah.com> (raw)
In-Reply-To: <1302800120-31560-1-git-send-email-segoon@openwall.com>

On Thu, Apr 14, 2011 at 08:55:19PM +0400, Vasiliy Kulikov wrote:
> page_count is copied from userspace.  agp_allocate_memory() tries to
> check whether this number is too big, but doesn't take into account the
> wrap case.  Also agp_create_user_memory() doesn't check whether
> alloc_size is calculated from num_agp_pages variable without overflow.
> This may lead to allocation of too small buffer with following buffer
> overflow.
> 
> Another problem in agp code is not addressed in the patch - kernel memory
> exhaustion (AGPIOC_RESERVE and AGPIOC_ALLOCATE ioctls).  It is not checked
> whether requested pid is a pid of the caller (no check in agpioc_reserve_wrap()).
> Each allocation is limited to 16KB, though, there is no per-process limit.
> This might lead to OOM situation, which is not even solved in case of the
> caller death by OOM killer - the memory is allocated for another (faked) process.
> 
> Signed-off-by: Vasiliy Kulikov <segoon@openwall.com>

David, what ever happened to this, and the other agp bugfix from
Vasiliy?

thanks,

greg k-h

> ---
>  drivers/char/agp/generic.c |    8 +++++++-
>  1 files changed, 7 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/char/agp/generic.c b/drivers/char/agp/generic.c
> index 745e7ba..342df51 100644
> --- a/drivers/char/agp/generic.c
> +++ b/drivers/char/agp/generic.c
> @@ -115,6 +115,9 @@ static struct agp_memory *agp_create_user_memory(unsigned long num_agp_pages)
>  	struct agp_memory *new;
>  	unsigned long alloc_size = num_agp_pages*sizeof(struct page *);
>  
> +	if (INT_MAX/sizeof(struct page *) < num_agp_pages)
> +		return NULL;
> +
>  	new = kzalloc(sizeof(struct agp_memory), GFP_KERNEL);
>  	if (new == NULL)
>  		return NULL;
> @@ -234,11 +237,14 @@ struct agp_memory *agp_allocate_memory(struct agp_bridge_data *bridge,
>  	int scratch_pages;
>  	struct agp_memory *new;
>  	size_t i;
> +	int cur_memory;
>  
>  	if (!bridge)
>  		return NULL;
>  
> -	if ((atomic_read(&bridge->current_memory_agp) + page_count) > bridge->max_memory_agp)
> +	cur_memory = atomic_read(&bridge->current_memory_agp);
> +	if ((cur_memory + page_count > bridge->max_memory_agp) ||
> +	    (cur_memory + page_count < page_count))
>  		return NULL;
>  
>  	if (type >= AGP_USER_TYPES) {
> -- 
> 1.7.0.4
> 
> _______________________________________________
> Security mailing list
> Security@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/security

  parent reply	other threads:[~2011-04-19 16:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14 16:55 [PATCH] char: agp: fix OOM and buffer overflow Vasiliy Kulikov
2011-04-14 17:07 ` Vasiliy Kulikov
2011-04-19 16:21 ` Greg KH [this message]
2011-04-19 17:48   ` Vasiliy Kulikov
2011-04-19 18:10     ` Greg KH
2011-04-19 20:29       ` Dave Airlie

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=20110419162157.GD23196@kroah.com \
    --to=greg@kroah.com \
    --cc=airlied@linux.ie \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@kernel.org \
    --cc=segoon@openwall.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