Linux Kernel: Missing Authorization
CVE-2022-30594 is a high-severity missing authorization vulnerability in Linux Kernel from Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 4.19.238, 5.4.189, 5.10.110 as the first without the flaw, so updating Linux Kernel to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.8% chance of exploitation within 30 days, higher than 57% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux Kernel to 4.19.238 or 5.4.189 or 5.10.110 or 5.15.33, whichever matches your release line, or a later version.
- Read the advisory on cdn.kernel.org for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux Kernel | before 4.19.238; 4.20 up to, but not including, 5.4.189; 5.5.0 up to, but not including, 5.10.110; 5.11 up to, but not including, 5.15.33; 5.16.0 up to, but not including, 5.16.19; 5.17 up to, but not including, 5.17.2 | 4.19.238, 5.4.189, 5.10.110, 5.15.33, 5.16.19, 5.17.2 |
| Debian | Debian Linux | 9.0; 10.0 | Not stated |
| NetApp | Solidfire, Enterprise Sds & Hci Storage Node | Not specified in the record | Not stated |
| NetApp | Solidfire & Hci Management Node | Not specified in the record | Not stated |
| NetApp | Hci Compute Node | Not specified in the record | Not stated |
| NetApp | 8300 Firmware | Not specified in the record | Not stated |
| NetApp | 8700 Firmware | Not specified in the record | Not stated |
| NetApp | A400 Firmware | Not specified in the record | Not stated |
| NetApp | H300s Firmware | Not specified in the record | Not stated |
| NetApp | H500s Firmware | Not specified in the record | Not stated |
| NetApp | H700s Firmware | Not specified in the record | Not stated |
| NetApp | H410s Firmware | Not specified in the record | Not stated |
| NetApp | H410c Firmware | Not specified in the record | Not stated |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 2.0 | 4.4 | Medium | NVD |
Official description
The Linux kernel before 5.17.2 mishandles seccomp permissions. The PTRACE_SEIZE code path allows attackers to bypass intended restrictions on setting the PT_SUSPEND_SECCOMP flag.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authorization
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
Patches and release notes
- bugs.chromium.org/p/project-zero/issues/detail?id=2276Exploit, Mailing List, Third Party Advisory
- github.com/torvalds/linux/commit/ee1fee900537b5d9560e9f937402de5ddc8412f3Third Party Advisory
Third-party and government advisories
- packetstormsecurity.com/files/167386/Kernel-Live-Patch-Security-Notice-LSN-0086-1.htmlThird Party Advisory, VDB Entry
- packetstormsecurity.com/files/170362/Linux-PT_SUSPEND_SECCOMP-Permission-Bypass-Ptracer-Death-Race.htmlThird Party Advisory, VDB Entry
- lists.debian.org/debian-lts-announce/2022/07/msg00000.htmlMailing List, Third Party Advisory
- security.netapp.com/advisory/ntap-20220707-0001/Third Party Advisory
- debian.org/security/2022/dsa-5173Third Party Advisory
Other vulnerabilities in Linux Kernel
- 9.8 Critical severity
- 7.0 High severity
- 7.8 High severity
- 7.1 High severity
- 7.0 High severity
- 7.8 High severity
Recent Missing Authorization vulnerabilities
- 8.8 High severity
- 7.8 High severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.