<?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 14:20:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50091 — locking/csd_lock: Change csdlock_debug from early_param to __setup</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50091</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;locking/csd_lock: Change csdlock_debug from early_param to __setup&lt;/p&gt;
&lt;p&gt;The csdlock_debug kernel-boot parameter is parsed by the
early_param() function csdlock_debug().  If set, csdlock_debug()
invokes static_branch_enable() to enable csd_lock_wait feature, which
triggers a panic on arm64 for kernels built with CONFIG_SPARSEMEM=y and
CONFIG_SPARSEMEM_VMEMMAP=n.&lt;/p&gt;
&lt;p&gt;With CONFIG_SPARSEMEM_VMEMMAP=n, __nr_to_section is called in
static_key_enable() and returns NULL, resulting in a NULL dereference
because mem_section is initialized only later in sparse_init().&lt;/p&gt;
&lt;p&gt;This is also a problem for powerpc because early_param() functions
are invoked earlier than jump_label_init(), also resulting in
static_key_enable() failures.  These failures cause the warning &amp;#34;static
key &amp;#39;xxx&amp;#39; used before call to jump_label_init()&amp;#34;.&lt;/p&gt;
&lt;p&gt;Thus, early_param is too early for csd_lock_wait to run
static_branch_enable(), so changes it to __setup to fix these.&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;locking/csd_lock: Change csdlock_debug from early_param to __setup&lt;/p&gt;
&lt;p&gt;The csdlock_debug kernel-boot parameter is parsed by the
early_param() function csdlock_debug().  If set, csdlock_debug()
invokes static_branch_enable() to enable csd_lock_wait feature, which
triggers a panic on arm64 for kernels built with CONFIG_SPARSEMEM=y and
CONFIG_SPARSEMEM_VMEMMAP=n.&lt;/p&gt;
&lt;p&gt;With CONFIG_SPARSEMEM_VMEMMAP=n, __nr_to_section is called in
static_key_enable() and returns NULL, resulting in a NULL dereference
because mem_section is initialized only later in sparse_init().&lt;/p&gt;
&lt;p&gt;This is also a problem for powerpc because early_param() functions
are invoked earlier than jump_label_init(), also resulting in
static_key_enable() failures.  These failures cause the warning &amp;#34;static
key &amp;#39;xxx&amp;#39; used before call to jump_label_init()&amp;#34;.&lt;/p&gt;
&lt;p&gt;Thus, early_param is too early for csd_lock_wait to run
static_branch_enable(), so changes it to __setup to fix these.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50091</guid>
    </item>
  </channel>
</rss>
