ZDF
Sign inSign up

Vulnerabilities

Vulnerability · 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 storage and runtime instrument

Published Jun 18, 2025 · catalog updated Oct 15, 2026 · Linux Linux

Check if you run it

No confirmed exploitation is on record for CVE-2022-49990. EPSS is 0.26%. Act only if a listed version of Linux Linux is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.26%
Remediation
Version ranges on file
Affected products
cpe linux/linux kernel · vendor Linux Linux 8d9047f8b967ce6181fd824ae922978e1b055cc0 <13cccafe0edcd03bf1c841de8ab8a1c8e34f77d9

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe linux/linux kernel6.0
  • vendor Linux Linux 8d9047f8b967ce6181fd824ae922978e1b055cc0 <13cccafe0edcd03bf1c841de8ab8a1c8e34f77d98d9047f8b967ce6181fd824ae922978e1b055cc0 <13cccafe0edcd03bf1c841de8ab8a1c8e34f77d9

How to fix CVE-2022-49990

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2022-49990. EPSS is 0.26%. Act only if a listed version of Linux Linux is installed.

Which versions are affected?

Compare what you have installed with linux/linux kernel 6.0; Linux Linux 8d9047f8b967ce6181fd824ae922978e1b055cc0 <13cccafe0edcd03bf1c841de8ab8a1c8e34f77d9 8d9047f8b967ce6181fd824ae922978e1b055cc0 <13cccafe0edcd03bf1c841de8ab8a1c8e34f77d9. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-415: Double Free. EPSS 0.26%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 18, 2025 · NIST NVD

    Detected

    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() ha

  2. Oct 15, 2026 · NIST NVD

    Updated

    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() ha

Sources

  • CVE.orgVulnerability recordCVE-2022-49990

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2022-49990

    30-day exploitation probability 0.3%

    first.org
  • EUVDVulnerability recordEUVD-2022-55269

    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 init

    euvd.enisa.europa.eu
  • NIST NVDVulnerability recordCVE-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 and runtime instrumentation control blocks are stored in the thread_struct of the associated task. These pointers are in

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.