Back

HIGH

kernel: seccompass mechanism bypass

Published May 8, 2019

Description

In the seccomp implementation prior to kernel version 4.8, there is a possible seccomp bypass due to seccomp policies that allow the use of ptrace. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android kernel Android ID: A-119769499

Affected products

Remediation

Red Hat statement

Red Hat has considers this CVE as with a 'Moderate' severity due specific conditions required to bypass seccomp. The attacker must have code execution privileges within the seccomp-restricted sandbox and the `ptrace` syscall should be allowed to be ran, from this perspective this CVE is understood more as a sandbox hardening issue than a important security flaw that'd impact system's core integrity. The outcomes of a possible exploitation is limited to process that are already running within an restricted environment. Additionally this behavior is clearly defined in the seccomp manual page. After reviewing this CVE, Red Hat Enterprise Linux 8 is marked as Not Affected. This decision is based in the fact of the Linux Kernel version shipped already contains the necessary patches which changes the execution order between ptrace and seccomp calls, making seccomp validates and eventual system call changes executed by the ptrace functionality.

Weaknesses (1)

References (9)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner google_android
Published May 8, 2019
Updated Aug 4, 2024
Reserved Dec 10, 2018
NVD
Status Modified
Modified Jun 17, 2026
Red Hat
Severity Moderate
Public date May 1, 2019