Bug 2066652

Summary: Kernel: seccomp PT_SUSPEND_SECCOMP permission bypass
Product: [Other] Security Response Reporter: Rohit Keshri <rkeshri>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: acaringi, adscvr, airlied, alciregi, bhu, brdeoliv, bskeggs, chwhite, crwood, ddepaula, debarbos, dhoward, dvlasenk, fhrbata, hdegoede, hkrzesin, hpa, jarod, jarodwilson, jfaracco, jferlan, jforbes, jglisse, jlelli, joe.lawrence, jonathan, josef, jshortt, jstancek, jwboyer, jwyatt, kcarcia, kernel-maint, kernel-mgr, lgoncalv, linville, lzampier, masami256, mchehab, nmurray, ptalbert, qzhao, rvrbovsk, scweaver, security-response-team, steved, tyberry, walters, williams
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-17 09:51:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2066648    

Description Rohit Keshri 2022-03-22 09:41:47 UTC 
The PT_SUSPEND_SECCOMP ptrace flag, which suppresses all seccomp checks for a process on kernels with CONFIG_CHECKPOINT_RESTORE, is supposed to only be settable by a ptracer with global CAP_SYS_ADMIN and no seccomp restrictions, but this is only enforced on the PTRACE_SETOPTIONS path. The PTRACE_SEIZE path can set the same flag, but doesn't do the privilege checks.
Comment 4 Rohit Keshri 2022-08-17 09:51:17 UTC 

*** This bug has been marked as a duplicate of bug 2085300 ***