Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] spice: add upstream security fixes for CVE-2017-7506
Date: Fri, 14 Jul 2017 21:41:54 +0200	[thread overview]
Message-ID: <87pod2ajr1.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170714193046.5dedfd97@windsurf> (Thomas Petazzoni's message of "Fri, 14 Jul 2017 19:30:46 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 > Hello,
 > On Fri, 14 Jul 2017 16:02:03 +0200, Peter Korsgaard wrote:
 >> Fixes CVE-2017-7506 - Possible buffer overflow via invalid monitor
 >> configurations.
 >> 
 >> For more details, see:
 >> https://marc.info/?l=oss-security&m=150001782924095
 >> 
 >> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
 >> ---
 >> ...nect-when-receiving-overly-big-ClientMoni.patch | 75 ++++++++++++++++++++++
 >> ...integer-overflows-handling-monitor-config.patch | 31 +++++++++
 >> ...buffer-overflows-handling-monitor-configu.patch | 48 ++++++++++++++
 >> 3 files changed, 154 insertions(+)
 >> create mode 100644 package/spice/0004-reds-Disconnect-when-receiving-overly-big-ClientMoni.patch
 >> create mode 100644 package/spice/0005-reds-Avoid-integer-overflows-handling-monitor-config.patch
 >> create mode 100644 package/spice/0006-reds-Avoid-buffer-overflows-handling-monitor-configu.patch

 > Applied to master, thanks. However, you forgot to use "git format-patch
 > -N" to generate the patches, so I removed the numbering from the patch
 > titles.

Crap, indeed :/ Sorry, and thanks for fixing it!

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-07-14 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 14:02 [Buildroot] [PATCH] spice: add upstream security fixes for CVE-2017-7506 Peter Korsgaard
2017-07-14 17:30 ` Thomas Petazzoni
2017-07-14 19:41   ` Peter Korsgaard [this message]
2017-07-19 16:16 ` Peter Korsgaard

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=87pod2ajr1.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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