<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 19:09:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-41932 — sched: fix warning in sched_setaffinity</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-41932</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched: fix warning in sched_setaffinity&lt;/p&gt;
&lt;p&gt;Commit 8f9ea86fdf99b added some logic to sched_setaffinity that included
a WARN when a per-task affinity assignment races with a cpuset update.&lt;/p&gt;
&lt;p&gt;Specifically, we can have a race where a cpuset update results in the
task affinity no longer being a subset of the cpuset. That&amp;#39;s fine; we
have a fallback to instead use the cpuset mask. However, we have a WARN
set up that will trigger if the cpuset mask has no overlap at all with
the requested task affinity. This shouldn&amp;#39;t be a warning condition; its
trivial to create this condition.&lt;/p&gt;
&lt;p&gt;Reproduced the warning by the following setup:&lt;/p&gt;
&lt;p&gt;- $PID inside a cpuset cgroup
- another thread repeatedly switching the cpuset cpus from 1-2 to just 1
- another thread repeatedly setting the $PID affinity (via taskset) to 2&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched: fix warning in sched_setaffinity&lt;/p&gt;
&lt;p&gt;Commit 8f9ea86fdf99b added some logic to sched_setaffinity that included
a WARN when a per-task affinity assignment races with a cpuset update.&lt;/p&gt;
&lt;p&gt;Specifically, we can have a race where a cpuset update results in the
task affinity no longer being a subset of the cpuset. That&amp;#39;s fine; we
have a fallback to instead use the cpuset mask. However, we have a WARN
set up that will trigger if the cpuset mask has no overlap at all with
the requested task affinity. This shouldn&amp;#39;t be a warning condition; its
trivial to create this condition.&lt;/p&gt;
&lt;p&gt;Reproduced the warning by the following setup:&lt;/p&gt;
&lt;p&gt;- $PID inside a cpuset cgroup
- another thread repeatedly switching the cpuset cpus from 1-2 to just 1
- another thread repeatedly setting the $PID affinity (via taskset) to 2&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-41932</guid>
    </item>
  </channel>
</rss>
