CVE-2022-49990
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-14
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.0 |
| linux | linux_kernel | 6.0 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-415 | The product calls free() twice on the same memory address. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a double free issue in the Linux kernel on the s390 architecture. When a fork() system call fails after duplicating a task_struct but before completing the thread copy, the newly allocated task and its thread_struct memory are freed twice because pointers to guarded storage and runtime instrumentation control blocks still reference memory from the original task. This can cause kernel crashes or memory corruption.
How can this vulnerability impact me? :
This vulnerability can lead to kernel crashes or memory corruption on affected systems, potentially causing system instability or denial of service. It may manifest as BUG_ON() errors or KASAN splats during certain syscall fuzz testing on s390x systems.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the fix for the double free of GS and RI CBs on fork() failure on s390x architecture has been applied. This fix involves clearing the associated pointer fields in arch_dup_task_struct() immediately after the new task is copied. Additionally, enabling CONFIG_SLAB_FREELIST_HARDENED and KASAN can help detect related issues during testing.