2fb549c388
>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>
(cherry picked from commit 02300786c2)
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
15 lines
438 B
Makefile
15 lines
438 B
Makefile
################################################################################
|
|
#
|
|
# libseccomp
|
|
#
|
|
################################################################################
|
|
|
|
LIBSECCOMP_VERSION = v2.4.0
|
|
LIBSECCOMP_SITE = $(call github,seccomp,libseccomp,$(LIBSECCOMP_VERSION))
|
|
LIBSECCOMP_LICENSE = LGPL-2.1
|
|
LIBSECCOMP_LICENSE_FILES = LICENSE
|
|
LIBSECCOMP_INSTALL_STAGING = YES
|
|
LIBSECCOMP_AUTORECONF = YES
|
|
|
|
$(eval $(autotools-package))
|