All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Salyzyn <salyzyn@android.com>
To: stable <stable@vger.kernel.org>
Cc: Seunghun Han <kkamagui@gmail.com>,
	Erik Schmauss <erik.schmauss@intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	kernel-team <kernel-team@android.com>
Subject: Re: ACPICA: acpi: acpica: fix acpi operand cache leak in nseval.c
Date: Wed, 9 May 2018 14:30:14 -0700	[thread overview]
Message-ID: <7ee79f5f-22dd-e637-1414-76e3d0715c4a@android.com> (raw)

ToT commit 97f3c0a4b0579b646b6b10ae5a3d59f0441cc12c

(ACPICA: acpi: acpica: fix acpi operand cache leak in nseval.c)

was assigned CVE-2017-13695 
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13695
and has been public since August 25 2017

Please apply to 3.18, 4.4 and 4.9 stable kernels for the reasons 
outlined in the body of the patch:

"This cache leak causes a security threat because an old kernel (<= 4.9) 
shows memory locations of kernel functions in stack dump. Some malicious 
users could use this information to neutralize kernel ASLR."

Bonus Points: Since the patch is ToT upstream, relieving the bug that 
results in the memory leak, even despite the non-CVE security status for 
<=4.12 kernels, it may be advised to also include this patch in 4.14.y 
stable as well.

Sincerely -- Mark Salyzyn

             reply	other threads:[~2018-05-09 21:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 21:30 Mark Salyzyn [this message]
2018-05-10  6:55 ` ACPICA: acpi: acpica: fix acpi operand cache leak in nseval.c Greg KH
2018-05-10 18:45   ` Schmauss, Erik
2018-05-11  5:23     ` Greg KH
2018-05-15 17:36       ` Schmauss, Erik
2018-05-15 20:42         ` Mark Salyzyn

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=7ee79f5f-22dd-e637-1414-76e3d0715c4a@android.com \
    --to=salyzyn@android.com \
    --cc=erik.schmauss@intel.com \
    --cc=kernel-team@android.com \
    --cc=kkamagui@gmail.com \
    --cc=rafael.j.wysocki@intel.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 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.