UPSTREAM: seccomp: cap SECCOMP_RET_ERRNO data to MAX_ERRNO
The value resulting from the SECCOMP_RET_DATA mask could exceed MAX_ERRNO when setting errno during a SECCOMP_RET_ERRNO filter action. This makes sure we have a reliable value being set, so that an invalid errno will not be ignored by userspace. Signed-off-by:Kees Cook <keescook@chromium.org> Reported-by:
Dmitry V. Levin <ldv@altlinux.org> Cc: Andy Lutomirski <luto@amacapital.net> Cc: Will Drewry <wad@chromium.org> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org> (cherry picked from commit 580c57f1076872ebc2427f898b927944ce170f2d) Signed-off-by:
Kees Cook <keescook@google.com> Change-Id: If82aa1b5f4be6375e8ca301d317d3d2db88a66dd Signed-off-by:
Chetan C R <cravin@codeaurora.org>
Loading
Please register or sign in to comment