CVE-2026-64182: Linux kernel · drivers/base/memory: fix memory block reference leak in poison accounting
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ce60d9452a0f2effa72fd20ea270c59ca691d455 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:03 UTC
Rated Low 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 ce60d9452a0f2effa72fd20ea270c59ca691d455, 24840b3139d7415144b81e4f9f4c44670d15bed9, 8502e2c2d0633f99d94d22ae8dabc10caae1fc2a +2
Exploitation evidence
Disclosed: evidence found.
CVE published 19 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
The issue is fixed in the Linux kernel versions identified by the provided commit hashes. Users should update to these fixed versions to remediate the vulnerability. No additional mitigation steps are indicated.
Description
A memory block reference leak vulnerability in the Linux kernel's drivers/base/memory subsystem has been fixed. The issue involved the functions memblk_nr_poison_inc() and memblk_nr_poison_sub() leaking device references by not dropping them after lookup via find_memory_block_by_id(). This flaw could lead to resource leaks in the kernel memory block accounting.
References
- git.kernel.org/stable/c/686b4283f82cd630fafd7ca9b03dfc080b3ec8fa (opens in a new tab)
- git.kernel.org/stable/c/ce60d9452a0f2effa72fd20ea270c59ca691d455 (opens in a new tab)
- git.kernel.org/stable/c/24840b3139d7415144b81e4f9f4c44670d15bed9 (opens in a new tab)
- git.kernel.org/stable/c/8502e2c2d0633f99d94d22ae8dabc10caae1fc2a (opens in a new tab)
- git.kernel.org/stable/c/03a2cc1756a0570f887d624cd6c535ea0cbd4951 (opens in a new tab)