linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: syzbot+ba2e91df8f74809417fa@syzkaller.appspotmail.com,
	syzbot+f3a0fa110fd630ab56c8@syzkaller.appspotmail.com,
	Trond Myklebust <trond.myklebust@hammerspace.com>,
	Anna Schumaker <anna.schumaker@netapp.com>,
	linux-nfs@vger.kernel.org, David Howells <dhowells@redhat.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	stable@vger.kernel.org
Subject: Re: [PATCH] NFS: fs_context: validate UDP retrans to prevent shift out-of-bounds
Date: Tue, 16 Mar 2021 15:35:53 -0700	[thread overview]
Message-ID: <b98720c9-2798-f168-eaaa-01d638d9900d@infradead.org> (raw)
In-Reply-To: <20210302001930.2253-1-rdunlap@infradead.org>

ping?

On 3/1/21 4:19 PM, Randy Dunlap wrote:
> Fix shift out-of-bounds in xprt_calc_majortimeo(). This is caused
> by a garbage timeout (retrans) mount option being passed to nfs mount,
> in this case from syzkaller.
> 
> If the protocol is XPRT_TRANSPORT_UDP, then 'retrans' is a shift
> value for a 64-bit long integer, so 'retrans' cannot be >= 64.
> If it is >= 64, fail the mount and return an error.
> 
> Fixes: 9954bf92c0cd ("NFS: Move mount parameterisation bits into their own file")
> Reported-by: syzbot+ba2e91df8f74809417fa@syzkaller.appspotmail.com
> Reported-by: syzbot+f3a0fa110fd630ab56c8@syzkaller.appspotmail.com
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Trond Myklebust <trond.myklebust@hammerspace.com>
> Cc: Anna Schumaker <anna.schumaker@netapp.com>
> Cc: linux-nfs@vger.kernel.org
> Cc: David Howells <dhowells@redhat.com>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Cc: stable@vger.kernel.org
> ---
>  fs/nfs/fs_context.c |   12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> --- lnx-512-rc1.orig/fs/nfs/fs_context.c
> +++ lnx-512-rc1/fs/nfs/fs_context.c
> @@ -974,6 +974,15 @@ static int nfs23_parse_monolithic(struct
>  			       sizeof(mntfh->data) - mntfh->size);
>  
>  		/*
> +		 * for proto == XPRT_TRANSPORT_UDP, which is what uses
> +		 * to_exponential, implying shift: limit the shift value
> +		 * to BITS_PER_LONG (majortimeo is unsigned long)
> +		 */
> +		if (!(data->flags & NFS_MOUNT_TCP)) /* this will be UDP */
> +			if (data->retrans >= 64) /* shift value is too large */
> +				goto out_invalid_data;
> +
> +		/*
>  		 * Translate to nfs_fs_context, which nfs_fill_super
>  		 * can deal with.
>  		 */
> @@ -1073,6 +1082,9 @@ out_no_address:
>  
>  out_invalid_fh:
>  	return nfs_invalf(fc, "NFS: invalid root filehandle");
> +
> +out_invalid_data:
> +	return nfs_invalf(fc, "NFS: invalid binary mount data");
>  }
>  
>  #if IS_ENABLED(CONFIG_NFS_V4)
> 


-- 
~Randy


  reply	other threads:[~2021-03-16 22:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02  0:19 [PATCH] NFS: fs_context: validate UDP retrans to prevent shift out-of-bounds Randy Dunlap
2021-03-16 22:35 ` Randy Dunlap [this message]
2021-03-16 23:19   ` Trond Myklebust

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=b98720c9-2798-f168-eaaa-01d638d9900d@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=anna.schumaker@netapp.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+ba2e91df8f74809417fa@syzkaller.appspotmail.com \
    --cc=syzbot+f3a0fa110fd630ab56c8@syzkaller.appspotmail.com \
    --cc=trond.myklebust@hammerspace.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).