Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Paulo Alcantara <paulo@paulo.ac>
To: Aurelien Aptel <aaptel@suse.com>, linux-cifs@vger.kernel.org
Cc: smfrench@gmail.com, Aurelien Aptel <aaptel@suse.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] CIFS: fix use-after-free of the lease keys
Date: Thu, 31 Jan 2019 10:52:29 -0200	[thread overview]
Message-ID: <87zhrhat0y.fsf@paulo.ac> (raw)
In-Reply-To: <20190131124607.2458-1-aaptel@suse.com>

Aurelien Aptel <aaptel@suse.com> writes:

> The request buffers are freed right before copying the pointers.
> Use the func args instead which are identical and still valid.
>
> Simple reproducer (requires KASAN enabled) on a cifs mount:
>
> echo foo > foo ; tail -f foo & rm foo
>
> Cc: <stable@vger.kernel.org> # 4.20
> Fixes: 179e44d49c2f ("smb3: add tracepoint for sending lease break responses to server")
> Signed-off-by: Aurelien Aptel <aaptel@suse.com>
> ---
>  fs/cifs/smb2pdu.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/cifs/smb2pdu.c b/fs/cifs/smb2pdu.c
> index 846e605175bf..54181387a770 100644
> --- a/fs/cifs/smb2pdu.c
> +++ b/fs/cifs/smb2pdu.c
> @@ -4435,8 +4435,8 @@ SMB2_lease_break(const unsigned int xid, struct cifs_tcon *tcon,
>  	rc = cifs_send_recv(xid, ses, &rqst, &resp_buf_type, flags, &rsp_iov);
>  	cifs_small_buf_release(req);
>  
> -	please_key_low = (__u64 *)req->LeaseKey;
> -	please_key_high = (__u64 *)(req->LeaseKey+8);
> +	please_key_low = (__u64 *)lease_key;
> +	please_key_high = (__u64 *)(lease_key+8);
>  	if (rc) {
>  		cifs_stats_fail_inc(tcon, SMB2_OPLOCK_BREAK_HE);
>  		trace_smb3_lease_err(le32_to_cpu(lease_state), tcon->tid,
> -- 
> 2.16.4

Reviewed-by: Paulo Alcantara <palcantara@suse.de>

Thanks!
Paulo

  reply	other threads:[~2019-01-31 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 12:46 [PATCH] CIFS: fix use-after-free of the lease keys Aurelien Aptel
2019-01-31 12:52 ` Paulo Alcantara [this message]
2019-01-31 15:53   ` Steve French

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=87zhrhat0y.fsf@paulo.ac \
    --to=paulo@paulo.ac \
    --cc=aaptel@suse.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=smfrench@gmail.com \
    --cc=stable@vger.kernel.org \
    /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