In the Linux kernel, the following vulnerability has been resolved: mm: shrinker: fix shrinker_info teardown race with expansion… (CVE-2026-64418)
A race condition vulnerability in the Linux kernel's memory management subsystem (shrinker) has been resolved. The issue involves improper synchronization during the teardown and expansion of shrinker_info structures, potentially leading to use-after-free or double-free conditions. This occurs because alloc_shrinker_info() releases a mutex prematurely during error cleanup, allowing concurrent access to partially freed memory. The fix ensures that teardown of shrinker_info is properly serialized with the shrinker_mutex, preventing these race conditions.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's memory management shrinker code arises from a race condition between expand_shrinker_info() and the teardown of shrinker_info arrays. Specifically, alloc_shrinker_info() drops the shrinker_mutex before freeing partially initialized shrinker_info arrays during error cleanup, which can lead to concurrent access and double-free or use-after-free scenarios. The flaw affects the handling of memcg (memory control groups) during their online transition. The patch serializes the teardown process with shrinker_mutex and keeps error cleanup within the locked section to prevent these races.
Potential Impact
This vulnerability can cause memory corruption in the kernel due to use-after-free or double-free conditions in the shrinker_info structures. Such corruption could potentially lead to system instability or crashes. No known exploits in the wild have been reported. The impact is limited to kernel memory management internals related to memory control groups.
Mitigation Recommendations
A fix has been implemented that serializes shrinker_info teardown with the shrinker_mutex and keeps alloc_shrinker_info() error cleanup inside the locked section. Users should apply the official Linux kernel updates that include this patch to remediate the vulnerability. Patch status is not yet confirmed from vendor advisory; check the official Linux kernel security advisories for the latest remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: mm: shrinker: fix shrinker_info teardown race with expansion… (CVE-2026-64418)
Description
A race condition vulnerability in the Linux kernel's memory management subsystem (shrinker) has been resolved. The issue involves improper synchronization during the teardown and expansion of shrinker_info structures, potentially leading to use-after-free or double-free conditions. This occurs because alloc_shrinker_info() releases a mutex prematurely during error cleanup, allowing concurrent access to partially freed memory. The fix ensures that teardown of shrinker_info is properly serialized with the shrinker_mutex, preventing these race conditions.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's memory management shrinker code arises from a race condition between expand_shrinker_info() and the teardown of shrinker_info arrays. Specifically, alloc_shrinker_info() drops the shrinker_mutex before freeing partially initialized shrinker_info arrays during error cleanup, which can lead to concurrent access and double-free or use-after-free scenarios. The flaw affects the handling of memcg (memory control groups) during their online transition. The patch serializes the teardown process with shrinker_mutex and keeps error cleanup within the locked section to prevent these races.
Potential Impact
This vulnerability can cause memory corruption in the kernel due to use-after-free or double-free conditions in the shrinker_info structures. Such corruption could potentially lead to system instability or crashes. No known exploits in the wild have been reported. The impact is limited to kernel memory management internals related to memory control groups.
Mitigation Recommendations
A fix has been implemented that serializes shrinker_info teardown with the shrinker_mutex and keeps alloc_shrinker_info() error cleanup inside the locked section. Users should apply the official Linux kernel updates that include this patch to remediate the vulnerability. Patch status is not yet confirmed from vendor advisory; check the official Linux kernel security advisories for the latest remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-q5wg-g4g8-xfhc
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64418"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420a9c2644c7f8083bc2
Added to database: 07/25/2026, 23:08:58 UTC
Last enriched: 07/25/2026, 23:25:52 UTC
Last updated: 07/26/2026, 04:03:27 UTC
Views: 5
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.