CVE-2026-72110
CVE CVE-2026-72110EUVD EUVD-2026-59068Published 2026-08-15T05:52:51.000ZLast changed 2026-08-17T05:40:23.000ZCVSS 7.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 0; a10787e6d58c24b51e91c19c6d16c5da89fcaa4b <9b51a6155d14389876916726430da30eabb1d4ed; a10787e6d58c24b51e91c19c6d16c5da89fcaa4b <c3fd6f28c7ce1142a3b23dbb840eaa4777de1d74; a10787e6d58c24b51e91c19c6d16c5da89fcaa4b <9cff220ddb65b022cc668bb652200742476e744c; patch: 6.6.145; a10787e6d58c24b51e91c19c6d16c5da89fcaa4b <43f0005f81b8ce3be962d653cde8db9022f1e9b0; 5.13; a10787e6d58c24b51e91c19c6d16c5da89fcaa4b <c4f626ddf2350652ad2f79daf1f10847f3f6eabd; patch: 7.1.5; patch: 7.2; patch: 6.18.40; patch: 6.12.97
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.