linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] bcache: Fix a NULL or wild pointer dereference in btree_gc_rewrite_node()
@ 2022-01-24 16:47 Zhou Qingyang
  2022-01-25  1:26 ` Coly Li
  2022-01-28 10:17 ` Greg KH
  0 siblings, 2 replies; 4+ messages in thread
From: Zhou Qingyang @ 2022-01-24 16:47 UTC (permalink / raw)
  To: zhou1615; +Cc: kjlu, Coly Li, Kent Overstreet, linux-bcache, linux-kernel

In btree_gc_rewrite_node(), btree_node_alloc_replacement() is assigned to
n and return error code or NULL on failure. n is passed to
bch_btree_node_write_sync() and there is a dereference of it in
bch_btree_node_write_sync() without checks, which may lead to wild
pointer dereference or NULL pointer dereference depending on n.

Fix this bug by adding IS_ERR_OR_NULL check of n.

This bug was found by a static analyzer.

Builds with 'make allyesconfig' show no new warnings,
and our static analyzer no longer warns about this code.

Fixes: ("bcache: Rework btree cache reserve handling")
Signed-off-by: Zhou Qingyang <zhou1615@umn.edu>
---
The analysis employs differential checking to identify inconsistent 
security operations (e.g., checks or kfrees) between two code paths 
and confirms that the inconsistent operations are not recovered in the
current function or the callers, so they constitute bugs. 

Note that, as a bug found by static analysis, it can be a false
positive or hard to trigger. Multiple researchers have cross-reviewed
the bug.

 drivers/md/bcache/btree.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/md/bcache/btree.c b/drivers/md/bcache/btree.c
index 88c573eeb598..06d42292e86c 100644
--- a/drivers/md/bcache/btree.c
+++ b/drivers/md/bcache/btree.c
@@ -1504,6 +1504,8 @@ static int btree_gc_rewrite_node(struct btree *b, struct btree_op *op,
 		return 0;
 
 	n = btree_node_alloc_replacement(replace, NULL);
+	if (IS_ERR_OR_NULL(n))
+		return 0;
 
 	/* recheck reserve after allocating replacement node */
 	if (btree_check_reserve(b, NULL)) {
-- 
2.25.1


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

* Re: [PATCH] bcache: Fix a NULL or wild pointer dereference in btree_gc_rewrite_node()
  2022-01-24 16:47 [PATCH] bcache: Fix a NULL or wild pointer dereference in btree_gc_rewrite_node() Zhou Qingyang
@ 2022-01-25  1:26 ` Coly Li
  2022-01-28 10:17 ` Greg KH
  1 sibling, 0 replies; 4+ messages in thread
From: Coly Li @ 2022-01-25  1:26 UTC (permalink / raw)
  To: Zhou Qingyang; +Cc: kjlu, Kent Overstreet, linux-bcache, linux-kernel

On 1/25/22 12:47 AM, Zhou Qingyang wrote:
> In btree_gc_rewrite_node(), btree_node_alloc_replacement() is assigned to
> n and return error code or NULL on failure. n is passed to
> bch_btree_node_write_sync() and there is a dereference of it in
> bch_btree_node_write_sync() without checks, which may lead to wild
> pointer dereference or NULL pointer dereference depending on n.
>
> Fix this bug by adding IS_ERR_OR_NULL check of n.
>
> This bug was found by a static analyzer.
>
> Builds with 'make allyesconfig' show no new warnings,
> and our static analyzer no longer warns about this code.
>
> Fixes: ("bcache: Rework btree cache reserve handling")
> Signed-off-by: Zhou Qingyang <zhou1615@umn.edu>
> ---
> The analysis employs differential checking to identify inconsistent
> security operations (e.g., checks or kfrees) between two code paths
> and confirms that the inconsistent operations are not recovered in the
> current function or the callers, so they constitute bugs.
>
> Note that, as a bug found by static analysis, it can be a false
> positive or hard to trigger. Multiple researchers have cross-reviewed
> the bug.
>
>   drivers/md/bcache/btree.c | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/drivers/md/bcache/btree.c b/drivers/md/bcache/btree.c
> index 88c573eeb598..06d42292e86c 100644
> --- a/drivers/md/bcache/btree.c
> +++ b/drivers/md/bcache/btree.c
> @@ -1504,6 +1504,8 @@ static int btree_gc_rewrite_node(struct btree *b, struct btree_op *op,
>   		return 0;
>   
>   	n = btree_node_alloc_replacement(replace, NULL);
> +	if (IS_ERR_OR_NULL(n))
> +		return 0;
>   

Hi Qingyang,

This is a valid fix with my first glance. I add this patch into my 
testing queue.

Thanks.

Coly Li


>   	/* recheck reserve after allocating replacement node */
>   	if (btree_check_reserve(b, NULL)) {


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

* Re: [PATCH] bcache: Fix a NULL or wild pointer dereference in btree_gc_rewrite_node()
  2022-01-24 16:47 [PATCH] bcache: Fix a NULL or wild pointer dereference in btree_gc_rewrite_node() Zhou Qingyang
  2022-01-25  1:26 ` Coly Li
@ 2022-01-28 10:17 ` Greg KH
  2022-01-28 14:34   ` Coly Li
  1 sibling, 1 reply; 4+ messages in thread
From: Greg KH @ 2022-01-28 10:17 UTC (permalink / raw)
  To: Zhou Qingyang; +Cc: kjlu, Coly Li, Kent Overstreet, linux-bcache, linux-kernel

On Tue, Jan 25, 2022 at 12:47:01AM +0800, Zhou Qingyang wrote:
> In btree_gc_rewrite_node(), btree_node_alloc_replacement() is assigned to
> n and return error code or NULL on failure. n is passed to
> bch_btree_node_write_sync() and there is a dereference of it in
> bch_btree_node_write_sync() without checks, which may lead to wild
> pointer dereference or NULL pointer dereference depending on n.
> 
> Fix this bug by adding IS_ERR_OR_NULL check of n.
> 
> This bug was found by a static analyzer.
> 
> Builds with 'make allyesconfig' show no new warnings,
> and our static analyzer no longer warns about this code.
> 
> Fixes: ("bcache: Rework btree cache reserve handling")
> Signed-off-by: Zhou Qingyang <zhou1615@umn.edu>
> ---
> The analysis employs differential checking to identify inconsistent 
> security operations (e.g., checks or kfrees) between two code paths 
> and confirms that the inconsistent operations are not recovered in the
> current function or the callers, so they constitute bugs. 
> 
> Note that, as a bug found by static analysis, it can be a false
> positive or hard to trigger. Multiple researchers have cross-reviewed
> the bug.
> 
>  drivers/md/bcache/btree.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/md/bcache/btree.c b/drivers/md/bcache/btree.c
> index 88c573eeb598..06d42292e86c 100644
> --- a/drivers/md/bcache/btree.c
> +++ b/drivers/md/bcache/btree.c
> @@ -1504,6 +1504,8 @@ static int btree_gc_rewrite_node(struct btree *b, struct btree_op *op,
>  		return 0;
>  
>  	n = btree_node_alloc_replacement(replace, NULL);
> +	if (IS_ERR_OR_NULL(n))
> +		return 0;
>  
>  	/* recheck reserve after allocating replacement node */
>  	if (btree_check_reserve(b, NULL)) {
> -- 
> 2.25.1
> 

As stated before, umn.edu is still not allowed to contribute to the
Linux kernel.  Please work with your administration to resolve this
issue.


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

* Re: [PATCH] bcache: Fix a NULL or wild pointer dereference in btree_gc_rewrite_node()
  2022-01-28 10:17 ` Greg KH
@ 2022-01-28 14:34   ` Coly Li
  0 siblings, 0 replies; 4+ messages in thread
From: Coly Li @ 2022-01-28 14:34 UTC (permalink / raw)
  To: Greg KH; +Cc: kjlu, Kent Overstreet, linux-bcache, linux-kernel, Zhou Qingyang

On 1/28/22 6:17 PM, Greg KH wrote:
> On Tue, Jan 25, 2022 at 12:47:01AM +0800, Zhou Qingyang wrote:
>> In btree_gc_rewrite_node(), btree_node_alloc_replacement() is assigned to
>> n and return error code or NULL on failure. n is passed to
>> bch_btree_node_write_sync() and there is a dereference of it in
>> bch_btree_node_write_sync() without checks, which may lead to wild
>> pointer dereference or NULL pointer dereference depending on n.
>>
>> Fix this bug by adding IS_ERR_OR_NULL check of n.
>>
>> This bug was found by a static analyzer.
>>
>> Builds with 'make allyesconfig' show no new warnings,
>> and our static analyzer no longer warns about this code.
>>
>> Fixes: ("bcache: Rework btree cache reserve handling")
>> Signed-off-by: Zhou Qingyang <zhou1615@umn.edu>
>> ---
>> The analysis employs differential checking to identify inconsistent
>> security operations (e.g., checks or kfrees) between two code paths
>> and confirms that the inconsistent operations are not recovered in the
>> current function or the callers, so they constitute bugs.
>>
>> Note that, as a bug found by static analysis, it can be a false
>> positive or hard to trigger. Multiple researchers have cross-reviewed
>> the bug.
>>
>>   drivers/md/bcache/btree.c | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/md/bcache/btree.c b/drivers/md/bcache/btree.c
>> index 88c573eeb598..06d42292e86c 100644
>> --- a/drivers/md/bcache/btree.c
>> +++ b/drivers/md/bcache/btree.c
>> @@ -1504,6 +1504,8 @@ static int btree_gc_rewrite_node(struct btree *b, struct btree_op *op,
>>   		return 0;
>>   
>>   	n = btree_node_alloc_replacement(replace, NULL);
>> +	if (IS_ERR_OR_NULL(n))
>> +		return 0;
>>   
>>   	/* recheck reserve after allocating replacement node */
>>   	if (btree_check_reserve(b, NULL)) {
>> -- 
>> 2.25.1
>>
> As stated before, umn.edu is still not allowed to contribute to the
> Linux kernel.  Please work with your administration to resolve this
> issue.
>

Copied. Thanks for the reminding.

Coly Li

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

end of thread, other threads:[~2022-01-28 14:34 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-24 16:47 [PATCH] bcache: Fix a NULL or wild pointer dereference in btree_gc_rewrite_node() Zhou Qingyang
2022-01-25  1:26 ` Coly Li
2022-01-28 10:17 ` Greg KH
2022-01-28 14:34   ` Coly Li

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).