<?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>Mon, 05 Oct 2026 05:44:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21919 — sched/fair: Fix potential memory corruption in child_cfs_rq_on_list</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21919</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched/fair: Fix potential memory corruption in child_cfs_rq_on_list&lt;/p&gt;
&lt;p&gt;child_cfs_rq_on_list attempts to convert a &amp;#39;prev&amp;#39; pointer to a cfs_rq.
This &amp;#39;prev&amp;#39; pointer can originate from struct rq&amp;#39;s leaf_cfs_rq_list,
making the conversion invalid and potentially leading to memory
corruption. Depending on the relative positions of leaf_cfs_rq_list and
the task group (tg) pointer within the struct, this can cause a memory
fault or access garbage data.&lt;/p&gt;
&lt;p&gt;The issue arises in list_add_leaf_cfs_rq, where both
cfs_rq-&amp;gt;leaf_cfs_rq_list and rq-&amp;gt;leaf_cfs_rq_list are added to the same
leaf list. Also, rq-&amp;gt;tmp_alone_branch can be set to rq-&amp;gt;leaf_cfs_rq_list.&lt;/p&gt;
&lt;p&gt;This adds a check `if (prev == &amp;amp;rq-&amp;gt;leaf_cfs_rq_list)` after the main
conditional in child_cfs_rq_on_list. This ensures that the container_of
operation will convert a correct cfs_rq struct.&lt;/p&gt;
&lt;p&gt;This check is sufficient because only cfs_rqs on the same CPU are added
to the list, so verifying the &amp;#39;prev&amp;#39; pointer against the current rq&amp;#39;s list
head is enough.&lt;/p&gt;
&lt;p&gt;Fixes a potential memory corruption issue that due to current struct
layout might not be manifesting as a crash but could lead to unpredictable
behavior when the layout changes.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sched/fair: Fix potential memory corruption in child_cfs_rq_on_list&lt;/p&gt;
&lt;p&gt;child_cfs_rq_on_list attempts to convert a &amp;#39;prev&amp;#39; pointer to a cfs_rq.
This &amp;#39;prev&amp;#39; pointer can originate from struct rq&amp;#39;s leaf_cfs_rq_list,
making the conversion invalid and potentially leading to memory
corruption. Depending on the relative positions of leaf_cfs_rq_list and
the task group (tg) pointer within the struct, this can cause a memory
fault or access garbage data.&lt;/p&gt;
&lt;p&gt;The issue arises in list_add_leaf_cfs_rq, where both
cfs_rq-&amp;gt;leaf_cfs_rq_list and rq-&amp;gt;leaf_cfs_rq_list are added to the same
leaf list. Also, rq-&amp;gt;tmp_alone_branch can be set to rq-&amp;gt;leaf_cfs_rq_list.&lt;/p&gt;
&lt;p&gt;This adds a check `if (prev == &amp;amp;rq-&amp;gt;leaf_cfs_rq_list)` after the main
conditional in child_cfs_rq_on_list. This ensures that the container_of
operation will convert a correct cfs_rq struct.&lt;/p&gt;
&lt;p&gt;This check is sufficient because only cfs_rqs on the same CPU are added
to the list, so verifying the &amp;#39;prev&amp;#39; pointer against the current rq&amp;#39;s list
head is enough.&lt;/p&gt;
&lt;p&gt;Fixes a potential memory corruption issue that due to current struct
layout might not be manifesting as a crash but could lead to unpredictable
behavior when the layout changes.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21919</guid>
    </item>
  </channel>
</rss>
