CVE-2022-49990
Last modified
CVE-2022-49990 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: s390: fix double free of GS and RI CBs on fork() failure The pointers for guarded storage and runtime instrumentation control blocks are stored in the thread_struct of the associated task. These pointers are initially copied on fork() via arch_dup_task_struct() and then cleared via copy_thread() before fork() returns. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: s390: fix double free of GS and RI CBs on fork() failure The pointers for guarded storage and runtime instrumentation control blocks are stored in the thread_struct of the associated task. These pointers are initially copied on fork() via arch_dup_task_struct() and then cleared via copy_thread() before fork() returns. If fork() happens to fail after the initial task dup and before copy_thread(), the newly allocated task and associated thread_struct memory are freed via free_task() -> arch_release_task_struct(). This results in a double free of the guarded storage and runtime info structs because the fields in the failed task still refer to memory associated with the source task. This problem can manifest as a BUG_ON() in set_freepointer() (with CONFIG_SLAB_FREELIST_HARDENED enabled) or KASAN splat (if enabled) when running trinity syscall fuzz tests on s390x. To avoid this problem, clear the associated pointer fields in arch_dup_task_struct() immediately after the new task is copied. Note that the RI flag is still cleared in copy_thread() because it resides in thread stack memory and that is where stack info is copied.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.4.105, < 4.5 | — |
| Linux | Linux Kernel | >= 4.9.68, < 4.10 | — |
| Linux | Linux Kernel | >= 4.14.5, < 4.19.257 | — |
| Linux | Linux Kernel | >= 4.20, < 5.4.212 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.140 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.64 | — |
| Linux | Linux Kernel | >= 5.16, < 5.19.6 | — |
| Linux | Linux Kernel | 6.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-49990?
How severe is CVE-2022-49990?
How do I fix CVE-2022-49990?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-49984In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49985In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2022-49986In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49987In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49988Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2022-49989In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49991In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49992In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49993In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49994In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49995In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-49996In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2022-49990?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
