Linux Kernel up to 7.2-rc1 BPF bpf_local_storage_destroy use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.2$0-$5k0.49

Summaryinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 6.6.144/6.12.96/6.18.39/7.1.4/7.2-rc1. Affected is the function bpf_local_storage_destroy of the component BPF. Executing a manipulation can lead to use after free. This vulnerability is tracked as CVE-2026-72110. The attack is restricted to local execution. No exploit exists.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 6.6.144/6.12.96/6.18.39/7.1.4/7.2-rc1 and classified as problematic. This vulnerability affects the function bpf_local_storage_destroy of the component BPF. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-72110 since 08/09/2026. The exploitation appears to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 08/15/2026).

Upgrading to version 6.6.145, 6.12.97, 6.18.40, 7.1.5 or 7.2-rc2 eliminates this vulnerability. Applying the patch c3fd6f28c7ce1142a3b23dbb840eaa4777de1d74/9cff220ddb65b022cc668bb652200742476e744c/c4f626ddf2350652ad2f79daf1f10847f3f6eabd/43f0005f81b8ce3be962d653cde8db9022f1e9b0/9b51a6155d14389876916726430da30eabb1d4ed is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.2

VulDB Base Score: 4.4
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.145/6.12.97/6.18.40/7.1.5/7.2-rc2
Patch: c3fd6f28c7ce1142a3b23dbb840eaa4777de1d74/9cff220ddb65b022cc668bb652200742476e744c/c4f626ddf2350652ad2f79daf1f10847f3f6eabd/43f0005f81b8ce3be962d653cde8db9022f1e9b0/9b51a6155d14389876916726430da30eabb1d4ed

Timelineinfo

08/09/2026 CVE reserved
08/15/2026 +6 days Advisory disclosed
08/15/2026 +0 days VulDB entry created
08/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-72110 (🔒)
GCVE (CVE): GCVE-0-2026-72110
GCVE (VulDB): GCVE-100-390532

Entryinfo

Created: 08/15/2026 12:25
Changes: 08/15/2026 12:25 (59)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Interested in the pricing of exploits?

See the underground prices here!