Linux Kernel up to 6.12.102/6.18.39/7.1.4 BPF Verifier check_mem_access memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 6.12.102/6.18.39/7.1.4. This impacts the function check_mem_access of the component BPF Verifier. Performing a manipulation results in memory corruption.
This vulnerability is identified as CVE-2026-72111. The attack is only possible with local access. There is not any exploit available.
Details
A vulnerability, which was classified as very critical, was found in Linux Kernel up to 6.12.102/6.18.39/7.1.4. This affects the function check_mem_access of the component BPF Verifier. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: bpf: Reset register bounds before narrowing retval range in check_mem_access() When the BPF verifier processes a context load of an LSM hook return value, it calls __mark_reg_s32_range() to narrow the register to the hook's valid range. However, __mark_reg_s32_range() intersects the new range with the register's existing bounds using max_t()/min_t() rather than replacing them. If the destination register carries stale bounds from a prior instruction (e.g. BPF_MOV64_IMM), the intersection can produce a range narrower than reality. The verifier then believes it knows the register's exact value, while at runtime the actual hook return value is loaded, creating a verifier/runtime mismatch that can be used to bypass BPF memory safety checks. The else branch already calls mark_reg_unknown() to reset register state before any narrowing. Apply the same reset in the is_retval path so stale bounds are cleared before __mark_reg_s32_range() intersects.
It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-72111 since 08/09/2026. The exploitability is told to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/26/2026).
The vulnerability scanner Nessus provides a plugin with the ID 339550 (Debian dsa-6466 : ata-modules-6.12.101+deb13-armmp-di - security update), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 6.12.103, 6.18.40, 7.1.5 or 7.2-rc1 eliminates this vulnerability. Applying the patch bde92f65042ec14389782dd223f706bf6b59ce5d/0993dc5fc619c0b25ab1310cb11d65e78351c0fe/5a55f9aecc08990940e70f0c7048a80850c5a16a/5e0b273e0a62cc04ec338c7b502797c66c2ed42a is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at Tenable (339550). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 6.12.102
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 7.1.0
- 7.1.1
- 7.1.2
- 7.1.3
- 7.1.4
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 339550
Nessus Name: Debian dsa-6466 : ata-modules-6.12.101+deb13-armmp-di - security update
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.12.103/6.18.40/7.1.5/7.2-rc1
Patch: bde92f65042ec14389782dd223f706bf6b59ce5d/0993dc5fc619c0b25ab1310cb11d65e78351c0fe/5a55f9aecc08990940e70f0c7048a80850c5a16a/5e0b273e0a62cc04ec338c7b502797c66c2ed42a
Timeline
08/09/2026 CVE reserved08/15/2026 Advisory disclosed
08/15/2026 VulDB entry created
08/26/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-72111 (🔒)
GCVE (CVE): GCVE-0-2026-72111
GCVE (VulDB): GCVE-100-390531
Entry
Created: 08/15/2026 12:24Updated: 08/26/2026 15:15
Changes: 08/15/2026 12:24 (59), 08/26/2026 15:15 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.