CVE-2026-64418

In the Linux kernel, the following vulnerability has been resolved: mm: shrinker: fix shrinker_info teardown race with expansion expand_shrinker_info() iterates all visible memcgs under shrinker_mutex, including memcgs that have not finished ->css_online() yet. Once pn->shrinker_info has been published, teardown must stay serialized with expand_shrinker_info() until that memcg is either fully online or no longer visible to iteration. Today alloc_shrinker_info() breaks that rule by dropping shrinker_mutex before freeing a partially initialized shrinker_info array, which may cause the following race: CPU0 CPU1 ==== ==== css_create --> list_add_tail_rcu(&css->sibling, &parent_css->children); online_css --> mem_cgroup_css_online --> alloc_shrinker_info --> alloc node0 info rcu_assign_pointer(C->node0->shrinker_info, old0) alloc node1 info -> FAIL -> goto err mutex_unlock(shrinker_mutex) shrinker_alloc() --> shrinker_memcg_alloc --> mutex_lock(shrinker_mutex) expand_shrinker_info --> mem_cgroup_iter see the memcg expand_one_shrinker_info --> old0 = C->node0->shrinker_info memcpy(new->unit, old0->unit, ...); free_shrinker_info --> kvfree(old0); /* double free !! */ kvfree_rcu(old0, rcu); The same problem exists later in mem_cgroup_css_online(). If alloc_shrinker_info() succeeds but a subsequent objcg allocation fails, the free_objcg -> free_shrinker_info() unwind path tears down the already published pn->shrinker_info arrays without shrinker_mutex. The expand_one_shrinker_info() can race with that teardown in the same way, leading to use-after-free or double-free of the old shrinker_info. Fix this by serializing shrinker_info teardown with shrinker_mutex, and by keeping alloc_shrinker_info() error cleanup inside the locked section.

• CWE-362

• https://git.kernel.org/stable/c/284c267f013e45d8c89d9fb9373105dc8e6c0947Patch
• https://git.kernel.org/stable/c/6465ff3ce65131c774a312d450abe10f4b9f3875Patch
• https://git.kernel.org/stable/c/65476d31d8056e859c48580f82295ce159196ffePatch
• https://git.kernel.org/stable/c/b9a280a9a454ed514636351d53fe2a233dc5054bPatch

Published

Jul 25, 2026

Last Modified

Sep 4, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-64412In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2026-64413In the Linux kernel, the following vulnerability has been re…7
• CVE-2026-64414In the Linux kernel, the following vulnerability has been re…7.5
• CVE-2026-64415In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-64416In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-64417In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-64419In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-6442Improper validation of bash commands in Snowflake Cortex Cod…8.3
• CVE-2026-64420In the Linux kernel, the following vulnerability has been re…7
• CVE-2026-64421In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-64422In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2026-64423In the Linux kernel, the following vulnerability has been re…7.8