GHSA-79J5-369G-HX4M
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 15:31In the Linux kernel, the following vulnerability has been resolved:
ftrace: fork: Initialize function graph state before copy_exec_state()
dup_task_struct() copies the parent's task_struct, including ret_stack. ftrace_graph_init_task() clears the copied function graph state, but it currently runs after copy_exec_state().
For non-CLONE_VM forks, copy_exec_state() allocates a new task_exec_state. If that allocation fails, copy_process() reaches bad_fork_free and free_task() calls ftrace_graph_exit_task(). Since the child still carries the parent's ret_stack pointer, the unwind frees the parent's active function graph return stack. The parent subsequently accesses freed memory from function_graph_enter_regs().
KASAN reports:
[ 22.190920] ================================================================== [ 22.195899] BUG: KASAN: slab-use-after-free in function_graph_enter_regs+0xa76/0xb90 [ 22.200747] Write of size 8 at addr ff110000054dc0a8 by task repro/1 [ 22.205134] [ 22.210770] CPU: 0 UID: 0 PID: 1 Comm: repro Not tainted 7.2.0-07732-g9328b3b03bdc-dirty #3 PREEMPT(lazy) [ 22.212576] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 22.213750] Call Trace: [ 22.215271] [ 22.216242] ? ftrace_stub_direct_tramp+0x10/0x10 [ 22.217774] dump_stack_lvl+0x4e/0x70 [ 22.220531] print_report+0x157/0x4b4 [ 22.223202] ? fixup_red_left+0x9/0x30 [ 22.224407] ? complete_report_info+0x83/0x110 [ 22.226679] ? function_graph_enter_regs+0xa76/0xb90 [ 22.228084] kasan_report+0xce/0x100 [ 22.230109] ? function_graph_enter_regs+0xa76/0xb90 [ 22.232860] ? stack_trace_save+0x4/0xd0 [ 22.234156] function_graph_enter_regs+0xa76/0xb90 [ 22.236090] ? kasan_save_stack+0x30/0x50 [ 22.237752] ? __pfx_function_graph_enter_regs+0x10/0x10 [ 22.238694] ? ring_buffer_lock_reserve+0x345/0xf80 [ 22.239628] ? stack_trace_save+0x4/0xd0 [ 22.242121] ? stack_trace_save+0x4/0xd0 [ 22.243588] ftrace_graph_func+0xda/0x160 [ 22.245362] ? ftrace_stub_direct_tramp+0x10/0x10 [ 22.246520] 0xffffffffa0000095 [ 22.250528] ? stack_trace_save+0x9/0xd0 [ 22.251757] ? ring_buffer_unlock_commit+0x11d/0x5c0 [ 22.253152] stack_trace_save+0x9/0xd0 [ 22.254264] kasan_save_stack+0x30/0x50 [ 22.273631] kasan_save_track+0x14/0x30 [ 22.276763] kasan_save_free_info+0x3b/0x70 [ 22.278296] __kasan_slab_free+0x43/0x70 [ 22.280157] kmem_cache_free+0xbf/0x3b0 [ 22.282963] ? ftrace_stub_direct_tramp+0x10/0x10 [ 22.284001] free_task+0xa2/0x160 [ 22.285699] ? ftrace_stub_direct_tramp+0x10/0x10 [ 22.286752] copy_process+0x2aae/0x7bc0
Initialize the child function graph state immediately after dup_task_struct(), before the first fallible operation.
{
"affected": [],
"aliases": [
"CVE-2026-97937"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:21Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nftrace: fork: Initialize function graph state before copy_exec_state()\n\ndup_task_struct() copies the parent\u0027s task_struct, including ret_stack.\nftrace_graph_init_task() clears the copied function graph state, but it\ncurrently runs after copy_exec_state().\n\nFor non-CLONE_VM forks, copy_exec_state() allocates a new task_exec_state.\nIf that allocation fails, copy_process() reaches bad_fork_free and\nfree_task() calls ftrace_graph_exit_task(). Since the child still carries\nthe parent\u0027s ret_stack pointer, the unwind frees the parent\u0027s active\nfunction graph return stack. The parent subsequently accesses freed memory\nfrom function_graph_enter_regs().\n\nKASAN reports:\n\n[ 22.190920] ==================================================================\n[ 22.195899] BUG: KASAN: slab-use-after-free in function_graph_enter_regs+0xa76/0xb90\n[ 22.200747] Write of size 8 at addr ff110000054dc0a8 by task repro/1\n[ 22.205134]\n[ 22.210770] CPU: 0 UID: 0 PID: 1 Comm: repro Not tainted 7.2.0-07732-g9328b3b03bdc-dirty #3 PREEMPT(lazy)\n[ 22.212576] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[ 22.213750] Call Trace:\n[ 22.215271] \u003cTASK\u003e\n[ 22.216242] ? ftrace_stub_direct_tramp+0x10/0x10\n[ 22.217774] dump_stack_lvl+0x4e/0x70\n[ 22.220531] print_report+0x157/0x4b4\n[ 22.223202] ? fixup_red_left+0x9/0x30\n[ 22.224407] ? complete_report_info+0x83/0x110\n[ 22.226679] ? function_graph_enter_regs+0xa76/0xb90\n[ 22.228084] kasan_report+0xce/0x100\n[ 22.230109] ? function_graph_enter_regs+0xa76/0xb90\n[ 22.232860] ? stack_trace_save+0x4/0xd0\n[ 22.234156] function_graph_enter_regs+0xa76/0xb90\n[ 22.236090] ? kasan_save_stack+0x30/0x50\n[ 22.237752] ? __pfx_function_graph_enter_regs+0x10/0x10\n[ 22.238694] ? ring_buffer_lock_reserve+0x345/0xf80\n[ 22.239628] ? stack_trace_save+0x4/0xd0\n[ 22.242121] ? stack_trace_save+0x4/0xd0\n[ 22.243588] ftrace_graph_func+0xda/0x160\n[ 22.245362] ? ftrace_stub_direct_tramp+0x10/0x10\n[ 22.246520] 0xffffffffa0000095\n[ 22.250528] ? stack_trace_save+0x9/0xd0\n[ 22.251757] ? ring_buffer_unlock_commit+0x11d/0x5c0\n[ 22.253152] stack_trace_save+0x9/0xd0\n[ 22.254264] kasan_save_stack+0x30/0x50\n[ 22.273631] kasan_save_track+0x14/0x30\n[ 22.276763] kasan_save_free_info+0x3b/0x70\n[ 22.278296] __kasan_slab_free+0x43/0x70\n[ 22.280157] kmem_cache_free+0xbf/0x3b0\n[ 22.282963] ? ftrace_stub_direct_tramp+0x10/0x10\n[ 22.284001] free_task+0xa2/0x160\n[ 22.285699] ? ftrace_stub_direct_tramp+0x10/0x10\n[ 22.286752] copy_process+0x2aae/0x7bc0\n\nInitialize the child function graph state immediately after\ndup_task_struct(), before the first fallible operation.",
"id": "GHSA-79j5-369g-hx4m",
"modified": "2026-09-25T15:31:44Z",
"published": "2026-09-25T12:31:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97937"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/08cacffeef8f64f1a222c93467ca84f24a46c953"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1fadebbbf31f65beba353fa9d1373bf183e03fed"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.