CVE-2026-72111: bpf: Reset register bounds before narrowing retval range in check_mem_access()

Published Aug 15, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

bpf: Reset register bounds before narrowing retval range in checkmemaccess()

When the BPF verifier processes a context load of an LSM hook return value, it calls markregs32range() to narrow the register to the hook's valid range. However, markregs32range() intersects the new range with the register's existing bounds using maxt()/mint() rather than replacing them.

If the destination register carries stale bounds from a prior instruction (e.g. BPFMOV64IMM), 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 markregunknown() to reset register state before any narrowing. Apply the same reset in the isretval path so stale bounds are cleared before markregs32range() intersects.

Affected Software

1 affected component
Linux Linux kernel

Event History

Aug 15, 2026
CVE Published
via MITRE·05:52 AM
Data Sourced
via MITRE·05:52 AM
Description
Data Sourced
via NVD·06:21 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-72111?

The severity of CVE-2026-72111 is rated at 65.

2

How do I fix CVE-2026-72111?

To fix CVE-2026-72111, ensure that your Linux kernel is updated to the latest patched version that addresses this vulnerability.

3

What systems are affected by CVE-2026-72111?

CVE-2026-72111 affects systems running the vulnerable versions of the Linux kernel.

4

What is the impact of CVE-2026-72111?

The impact of CVE-2026-72111 involves improper handling of context load by the BPF verifier, which could lead to potential security risks.

5

When was CVE-2026-72111 published?

CVE-2026-72111 was published on August 15, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203