All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@google.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	ben@decadent.org.uk, dhowells@redhat.com,
	james.l.morris@oracle.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] KEYS: trusted: fix writing past end of buffer in" failed to apply to 4.9-stable tree
Date: Fri, 10 Nov 2017 11:21:49 -0800	[thread overview]
Message-ID: <20171110192149.GB99710@google.com> (raw)
In-Reply-To: <1510329406.3359.57.camel@linux.vnet.ibm.com>

On Fri, Nov 10, 2017 at 10:56:46AM -0500, Mimi Zohar wrote:
> On Fri, 2017-11-10 at 12:49 +0100, Greg KH wrote:
> > On Mon, Nov 06, 2017 at 06:06:19AM -0500, Mimi Zohar wrote:
> > > Hi Greg,
> > > 
> > > On Sun, 2017-11-05 at 15:18 +0100, gregkh@linuxfoundation.org wrote:
> > > > The patch below does not apply to the 4.9-stable tree.
> > > > If someone wants it applied there, or to any other stable or longterm
> > > > tree, then please email the backport, including the original git commit
> > > > id to <stable@vger.kernel.org>.
> > > > 
> > > > thanks,
> > > > 
> > > > greg k-h
> > > 
> > > This commit needs to prereq commit ee618b4619b7 "KEYS: trusted:
> > > sanitize all key material".
> > 
> > Thanks, that fixes the issue for 4.4 and 4.9, but not for 3.18 :(
> 
> Commit 146aa8b "KEYS: Merge the type-specific data with the payload
> data" introduced the change trusted_destroy(), but it is a rather big
> patch.
> 
> @@ -1114,12 +1114,12 @@ static long trusted_read(const struct key
> *key, char __user�
> *buffer,
> � */
> �static void trusted_destroy(struct key *key)
> �{
> -�������struct trusted_key_payload *p = key->payload.data;
> +�������struct trusted_key_payload *p = key->payload.data[0];
> �
> ��������if (!p)
> ����������������return;
> ��������memset(p->key, 0, p->key_len);
> -�������kfree(key->payload.data);
> +�������kfree(key->payload.data[0]);
> �}
> �
> Perhaps David has back ported this patch already. David? �Otherwise,
> Eric could you create a patch that applies directly to the stable tree
> linux-3.18.y?
> 

I'll send backports of "KEYS: trusted: sanitize all key material" and "KEYS:
trusted: fix writing past end of buffer in trusted_read()".  We don't need
"KEYS: Merge the type-specific data with the payload data", as far as I know; it
seems to be cleanup/refactoring only.

Eric

      reply	other threads:[~2017-11-10 19:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-05 14:18 FAILED: patch "[PATCH] KEYS: trusted: fix writing past end of buffer in" failed to apply to 4.9-stable tree gregkh
2017-11-06 11:06 ` Mimi Zohar
2017-11-10 11:49   ` Greg KH
2017-11-10 15:56     ` Mimi Zohar
2017-11-10 19:21       ` Eric Biggers [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=20171110192149.GB99710@google.com \
    --to=ebiggers@google.com \
    --cc=ben@decadent.org.uk \
    --cc=dhowells@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=james.l.morris@oracle.com \
    --cc=stable@vger.kernel.org \
    --cc=zohar@linux.vnet.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.