linux: In the Linux kernel, the following vulnerability has been resolved: bpf: Fix exception exit lock checking for subpro...
CVE-2026-31526 is fixed in 19 products on 1 platform, first by DEBIAN-CVE-2026-31526, released May 15, 2026. It is not reported as exploited. Patch Radar priority: Routine.
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix exception exit lock checking for subprogs process_bpf_exit_full() passes check_lock = !curframe to check_resource_leak(), which is false in cases when bpf_throw() is called from a static subprog. This makes check_resource_leak() to skip validation of active_rcu_locks, active_preempt_locks, and active_irq_id on exception exits from subprogs. At runtime bpf_throw() unwinds the stack via ORC without releasing any user-acquired locks, which may cause various issues as the result. Fix by setting check_lock = true for exception exits regardless of curframe, since exceptions bypass all intermediate frame cleanup. Update the error message prefix to "bpf_throw" for exception exits to distinguish them from normal BPF_EXIT. Fix reject_subprog_with_rcu_read_lock test which was previously passing for the wrong reason. Test program returned directly from the subprog call without closing the RCU section, so the error was triggered by the unclosed RCU lock on normal exit, not by bpf_throw. Update __msg annotations for affected tests to match the new "bpf_throw" error prefix. The spin_lock case is not affected because they are already checked [1] at the call site in do_check_insn() before bpf_throw can run. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/kernel/bpf/verifier.c?h=v7.0-rc4#n21098
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool6.18 · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| bpftool6.18-debuginfo · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| kernel-livepatch-6.18.25-52.107 · amzn 2023 | 1:1.0-0.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| kernel6.18 · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| kernel6.18-debuginfo · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| kernel6.18-debuginfo-common-aarch64 · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| kernel6.18-debuginfo-common-x86_64 · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| kernel6.18-devel · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| kernel6.18-headers · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| kernel6.18-modules-extra · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| kernel6.18-modules-extra-common · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| kernel6.18-tools · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| kernel6.18-tools-debuginfo · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| kernel6.18-tools-devel · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.115-2 | DEBIAN-CVE-2026-31526 | May 15, 2026 |
| linux · Debian 14 | 6.19.11-1 | DEBIAN-CVE-2026-31526 | May 15, 2026 |
| perf6.18 · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| perf6.18-debuginfo · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| python3-perf6.18 · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
| python3-perf6.18-debuginfo · amzn 2023 | 1:6.18.25-52.107.amzn2023 | ALAS2023-2026-1746 | May 25, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.