summaryrefslogtreecommitdiff
path: root/kernel/debug
diff options
context:
space:
mode:
authorWaiman Long <longman@redhat.com>2026-09-29 23:18:33 -0400
committerTejun Heo <tj@kernel.org>2026-09-30 07:36:57 -1000
commite06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469 (patch)
tree7fd40fab348f941fc5cbe2b3d82b4ec2eabcc237 /kernel/debug
parent31c88350b7dd1522792f726f79607f31bb55c50f (diff)
downloadlinux-next-e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469.tar.gz
linux-next-e06b678e3b4e12fdaa0b51a7a5a54abc5dbd6469.zip
cgroup/cpuset: Don't access cpuset_cgrp_subsys.root in is_in_v2_mode()
After seeing the patch [1] to guard is_in_v2_mode() with RCU, it makes me realize that is_in_v2_mode() may be called in a context where a new cgroup filesystem is being rebound with stale cpuset_cgrp_subsys.root pointer. Avoid this potential UaF situation by adding a new cpuset_v2_mode flag which is set when the cpuset_v2_mode mount option is used. This flag is written into only when cpuset_bind() is being called with a stable cpuset_cgrp_subsys.root value. The is_in_v2_mode() helper is modified to read the new cpuset_v2_mode flag instead of accessing cpuset_cgrp_subsys.root directly. [1] https://lore.kernel.org/lkml/20260929084124.626693-2-arighi@nvidia.com Fixes: b8d1b8ee93df ("cpuset: Allow v2 behavior in v1 cgroup") Signed-off-by: Waiman Long <longman@redhat.com> Reviewed-by: Ridong Chen <ridong.chen@linux.dev> Reviewed-by: Andrea Righi <arighi@nvidia.com> Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'kernel/debug')
0 files changed, 0 insertions, 0 deletions