<?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, 06 Oct 2026 11:31:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49090 — arch/arm64: Fix topology initialization for core scheduling</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49090</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;arch/arm64: Fix topology initialization for core scheduling&lt;/p&gt;
&lt;p&gt;Arm64 systems rely on store_cpu_topology() to call update_siblings_masks()
to transfer the toplogy to the various cpu masks. This needs to be done
before the call to notify_cpu_starting() which tells the scheduler about
each cpu found, otherwise the core scheduling data structures are setup
in a way that does not match the actual topology.&lt;/p&gt;
&lt;p&gt;With smt_mask not setup correctly we bail on `cpumask_weight(smt_mask) == 1`
for !leaders in:&lt;/p&gt;
&lt;p&gt;notify_cpu_starting()
   cpuhp_invoke_callback_range()
     sched_cpu_starting()
       sched_core_cpu_starting()&lt;/p&gt;
&lt;p&gt;which leads to rq-&amp;gt;core not being correctly set for !leader-rq&amp;#39;s.&lt;/p&gt;
&lt;p&gt;Without this change stress-ng (which enables core scheduling in its prctl
tests in newer versions -- i.e. with PR_SCHED_CORE support) causes a warning
and then a crash (trimmed for legibility):&lt;/p&gt;
&lt;p&gt;[ 1853.805168] ------------[ cut here ]------------
[ 1853.809784] task_rq(b)-&amp;gt;core != rq-&amp;gt;core
[ 1853.809792] WARNING: CPU: 117 PID: 0 at kernel/sched/fair.c:11102 cfs_prio_less+0x1b4/0x1c4
...
[ 1854.015210] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010
...
[ 1854.231256] Call trace:
[ 1854.233689]  pick_next_task+0x3dc/0x81c
[ 1854.237512]  __schedule+0x10c/0x4cc
[ 1854.240988]  schedule_idle+0x34/0x54&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;arch/arm64: Fix topology initialization for core scheduling&lt;/p&gt;
&lt;p&gt;Arm64 systems rely on store_cpu_topology() to call update_siblings_masks()
to transfer the toplogy to the various cpu masks. This needs to be done
before the call to notify_cpu_starting() which tells the scheduler about
each cpu found, otherwise the core scheduling data structures are setup
in a way that does not match the actual topology.&lt;/p&gt;
&lt;p&gt;With smt_mask not setup correctly we bail on `cpumask_weight(smt_mask) == 1`
for !leaders in:&lt;/p&gt;
&lt;p&gt;notify_cpu_starting()
   cpuhp_invoke_callback_range()
     sched_cpu_starting()
       sched_core_cpu_starting()&lt;/p&gt;
&lt;p&gt;which leads to rq-&amp;gt;core not being correctly set for !leader-rq&amp;#39;s.&lt;/p&gt;
&lt;p&gt;Without this change stress-ng (which enables core scheduling in its prctl
tests in newer versions -- i.e. with PR_SCHED_CORE support) causes a warning
and then a crash (trimmed for legibility):&lt;/p&gt;
&lt;p&gt;[ 1853.805168] ------------[ cut here ]------------
[ 1853.809784] task_rq(b)-&amp;gt;core != rq-&amp;gt;core
[ 1853.809792] WARNING: CPU: 117 PID: 0 at kernel/sched/fair.c:11102 cfs_prio_less+0x1b4/0x1c4
...
[ 1854.015210] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010
...
[ 1854.231256] Call trace:
[ 1854.233689]  pick_next_task+0x3dc/0x81c
[ 1854.237512]  __schedule+0x10c/0x4cc
[ 1854.240988]  schedule_idle+0x34/0x54&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49090</guid>
    </item>
  </channel>
</rss>
