public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] char: agp: fix OOM and buffer overflow
@ 2011-04-14 16:55 Vasiliy Kulikov
  2011-04-14 17:07 ` Vasiliy Kulikov
  2011-04-19 16:21 ` Greg KH
  0 siblings, 2 replies; 6+ messages in thread
From: Vasiliy Kulikov @ 2011-04-14 16:55 UTC (permalink / raw)
  To: linux-kernel; +Cc: security, David Airlie

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>
---
 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


^ permalink raw reply related	[flat|nested] 6+ messages in thread

* Re: [PATCH] char: agp: fix OOM and buffer overflow
  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
  1 sibling, 0 replies; 6+ messages in thread
From: Vasiliy Kulikov @ 2011-04-14 17:07 UTC (permalink / raw)
  To: linux-kernel

> -       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))
I should have said that current_memory_agp is already protected by
agp_fe.agp_mutex, so the patch doesn't break atomic operation
(otherwise there is also a race between the check and use of
current_memory_agp).

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] char: agp: fix OOM and buffer overflow
  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
  2011-04-19 17:48   ` Vasiliy Kulikov
  1 sibling, 1 reply; 6+ messages in thread
From: Greg KH @ 2011-04-19 16:21 UTC (permalink / raw)
  To: Vasiliy Kulikov, David Airlie; +Cc: linux-kernel, security

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] char: agp: fix OOM and buffer overflow
  2011-04-19 16:21 ` Greg KH
@ 2011-04-19 17:48   ` Vasiliy Kulikov
  2011-04-19 18:10     ` Greg KH
  0 siblings, 1 reply; 6+ messages in thread
From: Vasiliy Kulikov @ 2011-04-19 17:48 UTC (permalink / raw)
  To: Greg KH; +Cc: David Airlie, linux-kernel, security

On Tue, Apr 19, 2011 at 09:21 -0700, Greg KH wrote:
> David, what ever happened to this, and the other agp bugfix from
> Vasiliy?

I got emails that both fixes went into -mm.

Thanks,

-- 
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] char: agp: fix OOM and buffer overflow
  2011-04-19 17:48   ` Vasiliy Kulikov
@ 2011-04-19 18:10     ` Greg KH
  2011-04-19 20:29       ` Dave Airlie
  0 siblings, 1 reply; 6+ messages in thread
From: Greg KH @ 2011-04-19 18:10 UTC (permalink / raw)
  To: Vasiliy Kulikov; +Cc: David Airlie, linux-kernel, security

On Tue, Apr 19, 2011 at 09:48:13PM +0400, Vasiliy Kulikov wrote:
> On Tue, Apr 19, 2011 at 09:21 -0700, Greg KH wrote:
> > David, what ever happened to this, and the other agp bugfix from
> > Vasiliy?
> 
> I got emails that both fixes went into -mm.

That's good, but David needs to take them and push them to Linus...


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] char: agp: fix OOM and buffer overflow
  2011-04-19 18:10     ` Greg KH
@ 2011-04-19 20:29       ` Dave Airlie
  0 siblings, 0 replies; 6+ messages in thread
From: Dave Airlie @ 2011-04-19 20:29 UTC (permalink / raw)
  To: Greg KH; +Cc: Vasiliy Kulikov, linux-kernel, security


> On Tue, Apr 19, 2011 at 09:48:13PM +0400, Vasiliy Kulikov wrote:
> > On Tue, Apr 19, 2011 at 09:21 -0700, Greg KH wrote:
> > > David, what ever happened to this, and the other agp bugfix from
> > > Vasiliy?
> > 
> > I got emails that both fixes went into -mm.
> 
> That's good, but David needs to take them and push them to Linus...
> 
> 

I'm ruminating, while they are security fixes, I'm hesitant to push them 
ASAP, without further testing, the /dev/agpgart hasn't really been used
by much in around 5 years, so getting a userspace and hardware that can 
test it is quite a lot of fun, though I suppse on the other side, nobody 
will notice if it breaks anything for 2 years.

Dave.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2011-04-19 20:30 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2011-04-19 17:48   ` Vasiliy Kulikov
2011-04-19 18:10     ` Greg KH
2011-04-19 20:29       ` Dave Airlie

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox