CVE-2026-72110bpf,fork: wipe ->bpf_storage before bailouts that access it
- 7.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected a10787e6d58c24b51e91c19c6d16c5da89fcaa4b – < 7df67a4799067a59e6a2d53f8059a6be6e73e678
- affected a10787e6d58c24b51e91c19c6d16c5da89fcaa4b – < aff686efd38728e06daf12417a0d7ed454ce4cff
- affected a10787e6d58c24b51e91c19c6d16c5da89fcaa4b – < c3fd6f28c7ce1142a3b23dbb840eaa4777de1d74
- affected a10787e6d58c24b51e91c19c6d16c5da89fcaa4b – < 9cff220ddb65b022cc668bb652200742476e744c
- affected a10787e6d58c24b51e91c19c6d16c5da89fcaa4b – < c4f626ddf2350652ad2f79daf1f10847f3f6eabd
- affected a10787e6d58c24b51e91c19c6d16c5da89fcaa4b – < 43f0005f81b8ce3be962d653cde8db9022f1e9b0
- affected a10787e6d58c24b51e91c19c6d16c5da89fcaa4b – < 9b51a6155d14389876916726430da30eabb1d4ed
- affected 5.13
- unaffected < 5.13
- unaffected 5.15.217 – ≤ 5.15.*
- unaffected 6.1.184 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/7df67a4799067a59e6a2d53f8059a6be6e73e678 (opens in a new tab)
- https://git.kernel.org/stable/c/aff686efd38728e06daf12417a0d7ed454ce4cff (opens in a new tab)
- https://git.kernel.org/stable/c/c3fd6f28c7ce1142a3b23dbb840eaa4777de1d74 (opens in a new tab)
- https://git.kernel.org/stable/c/9cff220ddb65b022cc668bb652200742476e744c (opens in a new tab)
- https://git.kernel.org/stable/c/c4f626ddf2350652ad2f79daf1f10847f3f6eabd (opens in a new tab)
- https://git.kernel.org/stable/c/43f0005f81b8ce3be962d653cde8db9022f1e9b0 (opens in a new tab)
- https://git.kernel.org/stable/c/9b51a6155d14389876916726430da30eabb1d4ed (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59068 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72110)Record last updated .