CVE-2026-64419
CVE CVE-2026-64419EUVD EUVD-2026-48963Published 2026-07-25T08:50:58.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: mm/shrinker: do not hold RCU lock in shrinker_debugfs_count_show() Reading the debugfs "count" file of a memcg-aware shrinker can sleep inside an RCU read-side critical section: BUG: sleeping function called from invalid context at kernel/cgroup/rstat.c:421 RCU nest depth: 1, expected: 0 css_rstat_flush mem_cgroup_flush_stats zswap_shrinker_count shrinker_debugfs_count_show shrinker_debugfs_count_show() invokes the ->count_objects() callback under rcu_read_lock(). The zswap callback flushes memcg stats via css_rstat_flush(), which may sleep, so it must not run under RCU. The RCU lock is not needed here. mem_cgroup_iter() takes RCU internally and returns a memcg holding a css reference (dropped on the next iteration or by mem_cgroup_iter_break()), so the memcg stays alive without it. The shrinker is kept alive by the open debugfs file: shrinker_free() removes the debugfs entries via debugfs_remove_recursive(), which waits for in-flight readers to drain, before call_rcu(..., shrinker_free_rcu_cb). The sibling "scan" handler already invokes the sleeping ->scan_objects() callback with no RCU section. Drop the rcu_read_lock()/rcu_read_unlock().
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 7.2-rc1; patch: 0; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 <e441cbfbd0eaa6404278e985033c33caba4db767; patch: 7.1.4; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 <b902890c62d200b3509cb5e09cf1e0a66553c128; patch: 6.1.178; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 <2fed79f0fe8c8d28a972c290dbfd693c3546c8c4; 6.0; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 <560e21e8ccff813e84d05f6500907c549a3d6985; patch: 6.18.39; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 <de5f69b8dae8698ac5e48dfcd30017887cdf4e5a; 5035ebc644aec92d55d1bbfe042f35341e4bffb5 <86237e56091e70f09c0fbf217f9d9c0e08f556c4; patch: 6.12.96; patch: 6.6.145
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.