Bug 2085300 (CVE-2022-30594)
| Summary: | CVE-2022-30594 kernel: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Anten Skrabec <askrabec> |
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | acaringi, adscvr, airlied, alciregi, bdettelb, bhu, bskeggs, chwhite, crwood, ddepaula, dvlasenk, hdegoede, hkrzesin, hpa, jarod, jarodwilson, jburrell, jfaracco, jferlan, jforbes, jglisse, jlelli, joe.lawrence, jonathan, josef, jshortt, jstancek, jwboyer, jwyatt, kcarcia, kernel-maint, kernel-mgr, kyoshida, lgoncalv, linville, lzampier, masami256, mchehab, michal.skrivanek, mperina, nmurray, ptalbert, qzhao, rkeshri, rvrbovsk, scweaver, steved, vkumar, walters, williams, wmealing |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | kernel 3.1 | Doc Type: | If docs needed, set a value |
| Doc Text: |
A flaw was found in the Linux kernel. The PTRACE_SEIZE code path allows attackers to bypass intended restrictions on setting the PT_SUSPEND_SECCOMP flag, possibly disabling seccomp.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-16 18:52:34 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: | 2121269, 2121270, 2121271, 2121272, 2127875, 2127881, 2128033, 2128034 | ||
| Bug Blocks: | 2085301 | ||
|
Description
Anten Skrabec
2022-05-12 23:54:00 UTC
*** Bug 2066652 has been marked as a duplicate of this bug. *** I'm keeping this moderate, I see other distros and people doing CVSSv3 scores with C:H I:H A:H , which I don't see how that works... This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2022:7318 https://access.redhat.com/errata/RHSA-2022:7318 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2022:7319 https://access.redhat.com/errata/RHSA-2022:7319 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2023:0300 https://access.redhat.com/errata/RHSA-2023:0300 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2023:0334 https://access.redhat.com/errata/RHSA-2023:0334 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2023:2736 https://access.redhat.com/errata/RHSA-2023:2736 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2023:2951 https://access.redhat.com/errata/RHSA-2023:2951 This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2022-30594 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Extended Update Support Via RHSA-2024:0412 https://access.redhat.com/errata/RHSA-2024:0412 |