Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
run: Handle unknown syscalls as intended
The error-handling here was if (r < 0 && r == -EFAULT) but Alex says it was almost certainly intended to be if (r < 0 && r != -EFAULT) so that syscalls not known to libseccomp are not a fatal error. Instead of literally making that change, emit a debug message on -EFAULT so we can see what is going on. This temporarily weakens our defence against CVE-2021-41133 (GHSA-67h7-w3jq-vh4q) in order to avoid regressions: if the installed version of libseccomp does not know about the recently-added syscalls, but the kernel does, then we will not prevent non-native executables from using those syscalls. Resolves: flatpak#4458 Signed-off-by: Simon McVittie <smcv@collabora.com> (cherry picked from commit d419fa6) (cherry picked from commit 270701f)
- Loading branch information