Local console flooding via invalid RCU checks
Published Jul 25, 2026 · Updated Jul 25, 2026
Incorrect synchronization in Linux Kernel allows local users to flood debug-kernel consoles through sleepable BPF LPM-trie access. trie_lookup_elem() checks only classic or BH RCU state, while trie_update_elem() and trie_delete_elem() use plain rcu_dereference() despite sleepable programs holding only Tasks Trace RCU. The effect requires a debug kernel and a sleepable BPF LSM hook that touches an LPM trie; it produces repeated lockdep warnings but no use-after-free.
Summary
What happened
Incorrect synchronization in Linux Kernel allows local users to flood debug-kernel consoles through sleepable BPF LPM-trie access. trie_lookup_elem() checks only classic or BH RCU state, while trie_update_elem() and trie_delete_elem() use plain rcu_dereference() despite sleepable programs holding only Tasks Trace RCU. The effect requires a debug kernel and a sleepable BPF LSM hook that touches an LPM trie; it produces repeated lockdep warnings but no use-after-free.
The record
- CVE
- CVE-2026-64352
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-821, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.14
- Affected versionversion=694cea395fded425008e93cd90cfdf7a451674af <2f884d371fafea137afea504d49ee4a7c8d7985b
- Affected versionversion=694cea395fded425008e93cd90cfdf7a451674af <304ca50582f0c047370f85e13caec456f78c9fcc
- Affected versionversion=694cea395fded425008e93cd90cfdf7a451674af <57454944737f3ad9a8703aecbbb79713b513a94b
- Affected versionversion=694cea395fded425008e93cd90cfdf7a451674af <9bfdf4b81b0e56d47bc6c46c34a46638be716695
- Affected versionversion=694cea395fded425008e93cd90cfdf7a451674af <bd6ad9a6b30498d845413e863fb95c6fab3babe3
- Affected versionversion=694cea395fded425008e93cd90cfdf7a451674af <ec662a8b2cde01e76b37ccd4b992d0342299e69c
- Affected versionversion=694cea395fded425008e93cd90cfdf7a451674af <f0967d4f1ba4323a3cb7dc8fdba74dd3a8caaf04
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo