CVE-2026-64192: Linux kernel · bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in de984ea883405420fdc416ae8964b752df586970 : patch Linux kernel soon.
Data as of 6 Nov 2026, 17:03 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in de984ea883405420fdc416ae8964b752df586970, c76b8abce575e0c6e4096957220b4515ed847d89, a6f0643e4f63cfaa0d5d4a69de4f132eac4b8fe4 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available in multiple Linux kernel commits that introduce a check to prevent allocation of BPF inode storage maps if the BPF LSM is not initialized. Users should update to a fixed kernel version containing these commits to prevent this issue.
Description
A vulnerability in the Linux kernel allows privileged users to create BPF inode storage maps when the BPF LSM is uninitialized, leading to a kernel panic. This occurs because the inode security blob offset is not properly initialized, causing a NULL pointer dereference during cleanup. The issue is fixed by preventing map allocation if the BPF LSM is not initialized.
References
- git.kernel.org/stable/c/413b14b9623a2e6ee131c2b2152b304aeb04e378 (opens in a new tab)
- git.kernel.org/stable/c/a6d634f794c808a261eac7d5af023a7e06b9ecd8 (opens in a new tab)
- git.kernel.org/stable/c/721f669853bdbf46b475a81bb5d05d610f8c19de (opens in a new tab)
- git.kernel.org/stable/c/5337eebdf8c5d4810b1913047f078d2815d5645f (opens in a new tab)
- git.kernel.org/stable/c/de984ea883405420fdc416ae8964b752df586970 (opens in a new tab)
- git.kernel.org/stable/c/267fdd9b6530c399dfd996e1a0a7628b45baf9f0 (opens in a new tab)
- git.kernel.org/stable/c/c76b8abce575e0c6e4096957220b4515ed847d89 (opens in a new tab)
- git.kernel.org/stable/c/a6f0643e4f63cfaa0d5d4a69de4f132eac4b8fe4 (opens in a new tab)