linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Colin King <colin.king@canonical.com>,
	linux-mm@kvack.org, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] mm/vmalloc: fix read of uninitialized pointer area
Date: Mon, 22 Mar 2021 12:46:40 +1000	[thread overview]
Message-ID: <1616381157.eirpjq5f8p.astroid@bobo.none> (raw)
In-Reply-To: <20210318155955.18220-1-colin.king@canonical.com>

Excerpts from Colin King's message of March 19, 2021 1:59 am:
> From: Colin Ian King <colin.king@canonical.com>
> 
> There is a corner case where the sanity check of variable size fails
> and branches to label fail and shift can be less than PAGE_SHIFT
> causing area to never be assigned. This was picked up by static
> analysis as follows:
> 
>     1. var_decl: Declaring variable area without initializer.
>        struct vm_struct *area;
> 
>    ...
> 
>     2. Condition !size, taking true branch.
>        if (!size || (size >> PAGE_SHIFT) > totalram_pages())
>     3. Jumping to label fail.
>                goto fail;
> 
>     ...
> 
>     4. Condition shift > 12, taking false branch.
> 	fail:
> 		if (shift > PAGE_SHIFT) {
> 			shift = PAGE_SHIFT;
> 			align = real_align;
> 			size = real_size;
> 			goto again;
> 		}
> 
>      Uninitialized pointer read (UNINIT)
>      5. uninit_use: Using uninitialized value area.
>  		if (!area) {
> 			...
> 		}
> 
> Fix this by setting area to NULL to avoid the uninitialized read
> of area.
> 
> Addresses-Coverity: ("Uninitialized pointer read")
> Fixes: 92db9fec381b ("mm/vmalloc: hugepage vmalloc mappings")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>

Looks good to me.

Acked-by: Nicholas Piggin <npiggin@gmail.com>

Thanks,
Nick

> ---
>  mm/vmalloc.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 96444d64129a..4b415b4bb7ae 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2888,8 +2888,10 @@ void *__vmalloc_node_range(unsigned long size, unsigned long align,
>  	unsigned long real_align = align;
>  	unsigned int shift = PAGE_SHIFT;
>  
> -	if (!size || (size >> PAGE_SHIFT) > totalram_pages())
> +	if (!size || (size >> PAGE_SHIFT) > totalram_pages()) {
> +		area = NULL;
>  		goto fail;
> +	}
>  
>  	if (vmap_allow_huge && !(vm_flags & VM_NO_HUGE_VMAP) &&
>  			arch_vmap_pmd_supported(prot)) {
> -- 
> 2.30.2
> 
> 


      reply	other threads:[~2021-03-22  2:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 15:59 [PATCH][next] mm/vmalloc: fix read of uninitialized pointer area Colin King
2021-03-22  2:46 ` Nicholas Piggin [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=1616381157.eirpjq5f8p.astroid@bobo.none \
    --to=npiggin@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=colin.king@canonical.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).