CVE-2022-49990
published 2025-06-18CVE-2022-49990: 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…
PriorityP339high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.22%
12.6th percentile
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.
Affected
26 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.2-1 (bookworm) | linux 6.0.2-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 4.14.5 < 4.15 | 4.15 |
| linux | linux | >= 4.4.105 < 4.5 | 4.5 |
| linux | linux | >= 4.9.68 < 4.10 | 4.10 |
| linux | linux | >= 8d9047f8b967ce6181fd824ae922978e1b055cc0 < 25a95303b9e513cd2978aacc385d06e6fec23d07 | 25a95303b9e513cd2978aacc385d06e6fec23d07 |
| linux | linux | >= 8d9047f8b967ce6181fd824ae922978e1b055cc0 < cacd522e6652fbc2dc0cc6ae11c4e30782fef14b | cacd522e6652fbc2dc0cc6ae11c4e30782fef14b |
| linux | linux | >= 8d9047f8b967ce6181fd824ae922978e1b055cc0 < 297ae7e87a87a001dd3dfeac1cb26a42fd929708 | 297ae7e87a87a001dd3dfeac1cb26a42fd929708 |
| linux | linux | >= 8d9047f8b967ce6181fd824ae922978e1b055cc0 < 8195e065abf3df84eb0ad2987e76a40f21d1791c | 8195e065abf3df84eb0ad2987e76a40f21d1791c |
| linux | linux | >= 8d9047f8b967ce6181fd824ae922978e1b055cc0 < fbdc482d43eda40a70de4b0155843d5472f6de62 | fbdc482d43eda40a70de4b0155843d5472f6de62 |
| linux | linux | >= 8d9047f8b967ce6181fd824ae922978e1b055cc0 < 13cccafe0edcd03bf1c841de8ab8a1c8e34f77d9 | 13cccafe0edcd03bf1c841de8ab8a1c8e34f77d9 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.140-1 | 5.10.140-1 |
| linux | linux_kernel | >= 0 < 6.0.2-1 | 6.0.2-1 |
| linux | linux_kernel | >= 0 < 6.0.2-1 | 6.0.2-1 |
| linux | linux_kernel | >= 0 < 6.0.2-1 | 6.0.2-1 |
| linux | linux_kernel | >= 4.14.5 < 4.19.257 | 4.19.257 |
| linux | linux_kernel | >= 4.20 < 5.4.212 | 5.4.212 |
| linux | linux_kernel | >= 4.4.105 < 4.5 | 4.5 |
| linux | linux_kernel | >= 4.9.68 < 4.10 | 4.10 |
| linux | linux_kernel | >= 5.11 < 5.15.64 | 5.15.64 |
| linux | linux_kernel | >= 5.16 < 5.19.6 | 5.19.6 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-8px8-fjv5-9vgx: 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 guarde
ghsa_unreviewed·2025-06-18
CVE-2022-49990 [HIGH] CWE-415 GHSA-8px8-fjv5-9vgx: 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 guarde
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() i
OSV
CVE-2022-49990: 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
osv·2025-06-18·CVSS 7.8
CVE-2022-49990 [HIGH] CVE-2022-49990: 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
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 s
Red Hat
kernel: s390: fix double free of GS and RI CBs on fork() failure
vendor_redhat·2025-06-18·CVSS 7.8
CVE-2022-49990 [HIGH] kernel: s390: fix double free of GS and RI CBs on fork() failure
kernel: s390: fix double free of GS and RI CBs on fork() failure
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
Debian
CVE-2022-49990: linux - In the Linux kernel, the following vulnerability has been resolved: s390: fix d...
vendor_debian·2022·CVSS 7.8
CVE-2022-49990 [HIGH] CVE-2022-49990: linux - In the Linux kernel, the following vulnerability has been resolved: s390: fix d...
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 s
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/13cccafe0edcd03bf1c841de8ab8a1c8e34f77d9https://git.kernel.org/stable/c/25a95303b9e513cd2978aacc385d06e6fec23d07https://git.kernel.org/stable/c/297ae7e87a87a001dd3dfeac1cb26a42fd929708https://git.kernel.org/stable/c/8195e065abf3df84eb0ad2987e76a40f21d1791chttps://git.kernel.org/stable/c/cacd522e6652fbc2dc0cc6ae11c4e30782fef14bhttps://git.kernel.org/stable/c/fbdc482d43eda40a70de4b0155843d5472f6de62
2025-06-18
Published