CVE-2026-64352 Linux CVE debrief

Who should care

Defenders responsible for Linux kernel-based systems, particularly those using BPF-enabled applications or sleepable BPF LSMs, should assess exposure and prioritize patching vulnerable kernel versions to prevent potential lockdep warnings and ensure system stability.

Why it matters

This vulnerability can cause lockdep warnings on debug kernels when a sleepable BPF LSM touches an LPM trie, potentially impacting system stability and requiring verification of BPF-enabled application stability.

• Potential console spam on debug kernels
• Verification of BPF-enabled application stability
• Patching priority for vulnerable Linux kernel versions
• Monitoring system logs for lockdep warnings

Technical summary

The Linux kernel's BPF implementation incorrectly uses rcu_dereference_check() with rcu_read_lock_bh_held(), leading to lockdep warnings on debug kernels when sleepable BPF programs access LPM maps. This issue arises because sleepable BPF programs hold only rcu_read_lock_trace(), which is not recognized by rcu_dereference_check(). The problem is resolved by switching the annotation to bpf_rcu_lock_held(), which accepts all three contexts (classic, BH, Tasks Trace), and by annotating walks in trie_update_elem() and trie_delete_elem() with rcu_dereference_protected() since they are protected by trie->lock. This fix prevents lockdep warnings on debug kernels, ensuring system stability when using sleepable BPF LSMs

Defensive priority

Defenders should prioritize patching vulnerable Linux kernel versions, particularly those used in BPF-enabled applications or with sleepable BPF LSMs, to prevent potential lockdep warnings and ensure system stability.

Recommended defensive actions

• Patch vulnerable Linux kernel versions
• Verify BPF-enabled applications and sleepable BPF LSMs for potential exposure
• Monitor system logs for lockdep warnings
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by the incorrect use of rcu_dereference_check() in the Linux kernel's BPF implementation. The issue is resolved by switching to bpf_rcu_lock_held() and annotating walks with rcu_dereference_protected().

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.