https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 24 Oct 2026 16:58:25 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-98972 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>cgroup/cpuset: Don&#39;t access cpuset_cgrp_subsys.root in is_in_v2_mode()</p> <p>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.</p> <p>[1] https://lore.kernel.org/lkml/20260929084124.626693-2-arighi@nvidia.com</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>cgroup/cpuset: Don&#39;t access cpuset_cgrp_subsys.root in is_in_v2_mode()</p> <p>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.</p> <p>[1] https://lore.kernel.org/lkml/20260929084124.626693-2-arighi@nvidia.com</p> https://db.gcve.eu/vuln/fkie_cve-2026-98972 https://db.gcve.eu/vuln/ghsa-pv9v-q67q-mhqc <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>cgroup/cpuset: Don&#39;t access cpuset_cgrp_subsys.root in is_in_v2_mode()</p> <p>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.</p> <p>[1] https://lore.kernel.org/lkml/20260929084124.626693-2-arighi@nvidia.com</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>cgroup/cpuset: Don&#39;t access cpuset_cgrp_subsys.root in is_in_v2_mode()</p> <p>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.</p> <p>[1] https://lore.kernel.org/lkml/20260929084124.626693-2-arighi@nvidia.com</p> https://db.gcve.eu/vuln/ghsa-pv9v-q67q-mhqc https://db.gcve.eu/vuln/msrc_cve-2026-98972 msrc_CVE-2026-98972 https://db.gcve.eu/vuln/msrc_cve-2026-98972