s390: fix double free of GS and RI CBs on fork() failure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.5, 4.10, 4.15, 4.19.257, 5.4.212, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 8d9047f8b967ce6181fd824ae922978e1b055cc0 · fixed in 25a95303b9e513cd2978aacc385d06e6fec23d07; From 8d9047f8b967ce6181fd824ae922978e1b055cc0 · fixed in cacd522e6652fbc2dc0cc6ae11c4e30782fef14b; From 8d9047f8b967ce6181fd824ae922978e1b055cc0 · fixed in 297ae7e87a87a001dd3dfeac1cb26a42fd929708; From 8d9047f8b967ce6181fd824ae922978e1b055cc0 · fixed in 8195e065abf3df84eb0ad2987e76a40f21d1791c; From 8d9047f8b967ce6181fd824ae922978e1b055cc0 · fixed in fbdc482d43eda40a70de4b0155843d5472f6de62; From 8d9047f8b967ce6181fd824ae922978e1b055cc0 · fixed in 13cccafe0edcd03bf1c841de8ab8a1c8e34f77d9; From 4.4.105 · fixed in 4.5; From 4.9.68 · fixed in 4.10; From 4.14.5 · fixed in 4.15
- Linux Linux
4.15
- KernelLinux
From 4.15.0 · fixed in 4.19.257; From 4.20.0 · fixed in 5.4.212; From 5.5.0 · fixed in 5.10.140; From 5.11.0 · fixed in 5.15.64; From 5.16.0 · fixed in 5.19.6