From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libseccomp: security bump to version 2.4.0
Date: Sun, 24 Mar 2019 09:01:24 +0100 [thread overview]
Message-ID: <87va08bt0r.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190321074043.15989-1-peter@korsgaard.com> (Peter Korsgaard's message of "Thu, 21 Mar 2019 08:40:43 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> From the advisory:
> Jann Horn identified a problem in current versions of
> libseccomp where the library did not correctly generate 64-bit syscall
> argument comparisons using the arithmetic operators (LT, GT, LE, GE).
> Jann has done a search using codesearch.debian.net and it would appear
> that only systemd and Tor are using libseccomp in such a way as to
> trigger the bad code. In the case of systemd this appears to affect
> the socket address family and scheduling class filters. In the case
> of Tor it appears that the bad filters could impact the memory
> addresses passed to mprotect(2).
> The libseccomp v2.4.0 release fixes this problem, and should be a
> direct drop-in replacement for previous v2.x releases.
> https://www.openwall.com/lists/oss-security/2019/03/15/1
> v2.4.0 adds a new scmp_api_level utility, so update 0001-remove-static.patch
> to match.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-03-24 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 7:40 [Buildroot] [PATCH] package/libseccomp: security bump to version 2.4.0 Peter Korsgaard
2019-03-24 8:01 ` Peter Korsgaard [this message]
2019-03-27 21:51 ` 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=87va08bt0r.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.