All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/xen: add XSA-333..344 security fixes
Date: Tue, 08 Dec 2020 10:59:08 +0100	[thread overview]
Message-ID: <87im9cty8j.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20201121124206.24581-1-peter@korsgaard.com> (Peter Korsgaard's message of "Sat, 21 Nov 2020 13:42:06 +0100")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

 > Fixes the following security issues:
 > - XSA-333: x86 pv: Crash when handling guest access to MSR_MISC_ENABLE
 >   (CVE-2020-25602)
 >   https://xenbits.xenproject.org/xsa/advisory-333.html

 > - XSA-334: Missing unlock in XENMEM_acquire_resource error path
 >   (CVE-2020-25598)
 >   https://xenbits.xenproject.org/xsa/advisory-334.html

 > - XSA-336: race when migrating timers between x86 HVM vCPU-s
 >   (CVE-2020-25604)
 >   https://xenbits.xenproject.org/xsa/advisory-336.html

 > - XSA-337: PCI passthrough code reading back hardware registers
 >   (CVE-2020-25595)
 >   https://xenbits.xenproject.org/xsa/advisory-337.html

 > - XSA-338: once valid event channels may not turn invalid (CVE-2020-25597)
 >   https://xenbits.xenproject.org/xsa/advisory-338.html

 > - XSA-339: x86 pv guest kernel DoS via SYSENTER (CVE-2020-25596)
 >   https://xenbits.xenproject.org/xsa/advisory-339.html

 > - XSA-340: Missing memory barriers when accessing/allocating an event
 >   channel (CVE-2020-25603)
 >   https://xenbits.xenproject.org/xsa/advisory-340.html

 > - XSA-342: out of bounds event channels available to 32-bit x86 domains
 >   (CVE-2020-25600)
 >   https://xenbits.xenproject.org/xsa/advisory-342.html

 > - XSA-343: races with evtchn_reset() (CVE-2020-25599)
 >   https://xenbits.xenproject.org/xsa/advisory-343.html

 > - XSA-344: lack of preemption in evtchn_reset() / evtchn_destroy()
 >   (CVE-2020-25601)
 >   https://xenbits.xenproject.org/xsa/advisory-344.html

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

For 2020.02.x and 2020.08.x I have instead bumped to 4.13.2, which
contains security fixes up to XSA-347.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2020-12-08  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-21 12:42 [Buildroot] [PATCH] package/xen: add XSA-333..344 security fixes Peter Korsgaard
2020-11-22 14:31 ` Peter Korsgaard
2020-12-08  9:59 ` Peter Korsgaard [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=87im9cty8j.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 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.