From: Johannes Weiner <hannes@cmpxchg.org>
To: Rik van Riel <riel@surriel.com>
Cc: Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH] mm/memcg: fix UAF in drain_all_stock() async work during offline
Date: Thu, 27 Aug 2026 13:14:59 -0400 [thread overview]
Message-ID: <20260827171459.GE3004@cmpxchg.org> (raw)
In-Reply-To: <20260827124211.3b94b103@fangorn>
On Thu, Aug 27, 2026 at 12:42:11PM -0400, Rik van Riel wrote:
> drain_all_stock() queues drain work on remote CPUs via
> schedule_drain_work() -> queue_work_on(memcg_wq) and returns
> immediately without waiting. The worker, drain_local_memcg_stock()
> / drain_local_obj_stock(), dereferences per-CPU stock caches with
> READ_ONCE(stock->cached[i]) and does css_put() / obj_cgroup_put().
>
> mem_cgroup_css_offline() calls drain_all_stock(memcg) to
> optimize reclamation latency, but never flushes memcg_wq. If
> that races with cgroup removal, free can happen while workers
> are still pending, causing UAF. The drain work could also have
> been queued by somebody else before offline started (e.g. high
> throttling), not just by the offline path itself.
>
> Timeline illustrating the race:
>
> CPU0 (rmdir + offline) CPU1 (charge cache holder)
> ------------------------- ----------------------------
> cgroup_rmdir()
> cgroup_destroy_locked()
> kill_css_sync()
> ...
>
> refill_stock(victim)
> css_get(victim)
> WRITE_ONCE(cached[i]=victim)
I'm really confused. CPU1 acquires a ref for the cached[i] pointer ^
> percpu_ref kill confirmed, css_killed_ref_fn() called
>
> css_killed_work_fn() [offline_wq]
> mem_cgroup_css_offline(victim)
> drain_all_stock(victim)
> is_memcg_drain_needed()
> READ_ONCE(cached) -> victim
> queue_work_on(CPU1, memcg_wq, work)
> // no flush!
> mem_cgroup_private_id_put()
> css_put() -> refcnt may hit 0
So how can it hit 0 here?
> [RCU GP]
> css_free_rwork_fn()
> mem_cgroup_free(victim)
> // victim struct freed
This won't run until we hit zero...
>
> // worker delayed by scheduler/
> // WQ concurrency
> drain_local_memcg_stock()
> old = READ_ONCE(cached[i])
> // UAF: old == freed victim
> memcg_uncharge(old)
> css_put(&old->css)
...which is here.
next prev parent reply other threads:[~2026-08-27 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 16:42 Rik van Riel
2026-08-27 16:57 ` Shakeel Butt
2026-08-27 17:14 ` Johannes Weiner [this message]
2026-08-27 22:35 ` Andrew Morton
2026-08-28 2:33 ` Rik van Riel
2026-08-28 0:42 ` kernel test robot
2026-08-28 3:22 ` kernel test robot
2026-08-28 10:25 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260827171459.GE3004@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=riel@surriel.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®