CVE-2026-72111

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.

Package Linux Kernel
Published 2026-08-15
Last modified 2026-08-15
Patch available
Yes

Affected versions

Linux kernel versions 6.10.13, 6.11.2, 6.12 and later are affected. Fixed in 6.12.103, 6.18.40, 7.1.5, 7.2-rc1 and their respective stable series.

Affected from
≥ 6.10.13 ≥ 6.11.2 ≥ 6.12
Fixed in
✓ 6.12.103 6.12.x ✓ 6.18.40 6.18.x ✓ 7.1.5 7.1.x ✓ 7.2-rc1

Frequently asked questions

  • What is CVE-2026-72111?

    CVE-2026-72111 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.10.13 onward and has been patched in 6.12.103, 6.18.40, 7.1.5 and others. CVE-2026-72111 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2026-72111?

    Yes. CVE-2026-72111 has been patched. Fixed versions include 6.12.103, 6.18.40, 7.1.5 and others. If you are running Linux kernel 6.10.13 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-72111 actively exploited?

    No. CVE-2026-72111 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.