In the Linux kernel, the following vulnerability has been resolved: drivers/base/memory: fix memory block reference leak in poison accounting… (CVE-2026-64182)
A memory block reference leak vulnerability in the Linux kernel's drivers/base/memory component has been resolved. The functions memblk_nr_poison_inc() and memblk_nr_poison_sub() improperly handle references acquired via find_memory_block_by_id(), leading to a reference leak. This issue was fixed by ensuring the reference is dropped after updating the nr_hwpoison counter.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel involves a reference leak in memory block handling within the drivers/base/memory code. Specifically, memblk_nr_poison_inc() and memblk_nr_poison_sub() acquire a reference to a memory block device using find_memory_block_by_id() but fail to release this reference after use, causing a leak. The fix involves dropping the reference after updating the nr_hwpoison value to prevent resource leakage.
Potential Impact
The impact is a resource leak in the kernel memory block management subsystem, which could lead to increased memory consumption or resource exhaustion over time. There is no indication of direct exploitation or security compromise beyond the leak. No known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented to address this reference leak by properly releasing the memory block device reference after use. Since no patch links or vendor advisories are provided, users should monitor official Linux kernel updates for the inclusion of this fix and apply updates accordingly. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: drivers/base/memory: fix memory block reference leak in poison accounting… (CVE-2026-64182)
Description
A memory block reference leak vulnerability in the Linux kernel's drivers/base/memory component has been resolved. The functions memblk_nr_poison_inc() and memblk_nr_poison_sub() improperly handle references acquired via find_memory_block_by_id(), leading to a reference leak. This issue was fixed by ensuring the reference is dropped after updating the nr_hwpoison counter.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel involves a reference leak in memory block handling within the drivers/base/memory code. Specifically, memblk_nr_poison_inc() and memblk_nr_poison_sub() acquire a reference to a memory block device using find_memory_block_by_id() but fail to release this reference after use, causing a leak. The fix involves dropping the reference after updating the nr_hwpoison value to prevent resource leakage.
Potential Impact
The impact is a resource leak in the kernel memory block management subsystem, which could lead to increased memory consumption or resource exhaustion over time. There is no indication of direct exploitation or security compromise beyond the leak. No known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented to address this reference leak by properly releasing the memory block device reference after use. Since no patch links or vendor advisories are provided, users should monitor official Linux kernel updates for the inclusion of this fix and apply updates accordingly. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-pmqf-jjx9-qv6f
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64182"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a72a4a8d5989129dd3
Added to database: 07/19/2026, 19:38:15 UTC
Last enriched: 07/19/2026, 19:39:29 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 14
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.