CVE-2026-72110
In the Linux kernel, the following vulnerability has been resolved: bpf,fork: wipe ->bpf_storage before bailouts that access it Currently, copy_process() can bail out to free_task() before p->bpf_storage has been initialized, with this call graph (shown here for the !CONFIG_MEMCG case): copy_process dup_task_struct arch_dup_task_struct [copies the entire task_struct, including ->bpf_storage member] [RLIMIT_NPROC check fails] delayed_free_task free_task bpf_task_storage_free rcu_dereference(task->bpf_storage) bpf_local_storage_destroy In this case, the nascent task's ->bpf_storage member that bpf_local_storage_destroy() operates on is a plain copy of the parent's ->bpf_storage pointer, not a real initialized pointer. This leads to badness (kernel hangs, UAF). This is reachable as long as the process calling fork() has been inserted into a task storage map.
Affected versions
Linux kernel versions
5.13
and later are affected. Fixed in
6.6.145,
6.12.97,
6.18.40,
7.1.5,
7.2-rc2
and their respective stable series.
References
5 totalFrequently asked questions
-
What is CVE-2026-72110?
CVE-2026-72110 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.13 onward and has been patched in 6.6.145, 6.12.97, 6.18.40 and others. CVE-2026-72110 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-72110?
Yes. CVE-2026-72110 has been patched. Fixed versions include 6.6.145, 6.12.97, 6.18.40 and others. If you are running Linux kernel 5.13 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-72110 actively exploited?
No. CVE-2026-72110 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.