<?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>Fri, 02 Oct 2026 04:48:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53419 — rcu: Protect rcu_print_task_exp_stall() -&gt;exp_tasks access</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53419</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;rcu: Protect rcu_print_task_exp_stall() -&amp;gt;exp_tasks access&lt;/p&gt;
&lt;p&gt;For kernels built with CONFIG_PREEMPT_RCU=y, the following scenario can
result in a NULL-pointer dereference:&lt;/p&gt;
&lt;p&gt;CPU1                                           CPU2
rcu_preempt_deferred_qs_irqrestore                rcu_print_task_exp_stall
  if (special.b.blocked)                            READ_ONCE(rnp-&amp;gt;exp_tasks) != NULL
    raw_spin_lock_rcu_node
    np = rcu_next_node_entry(t, rnp)
    if (&amp;amp;t-&amp;gt;rcu_node_entry == rnp-&amp;gt;exp_tasks)
      WRITE_ONCE(rnp-&amp;gt;exp_tasks, np)
      ....
      raw_spin_unlock_irqrestore_rcu_node
                                                    raw_spin_lock_irqsave_rcu_node
                                                    t = list_entry(rnp-&amp;gt;exp_tasks-&amp;gt;prev,
                                                        struct task_struct, rcu_node_entry)
                                                    (if rnp-&amp;gt;exp_tasks is NULL, this
                                                       will dereference a NULL pointer)&lt;/p&gt;
&lt;p&gt;The problem is that CPU2 accesses the rcu_node structure&amp;#39;s-&amp;gt;exp_tasks
field without holding the rcu_node structure&amp;#39;s -&amp;gt;lock and CPU2 did
not observe CPU1&amp;#39;s change to rcu_node structure&amp;#39;s -&amp;gt;exp_tasks in time.
Therefore, if CPU1 sets rcu_node structure&amp;#39;s-&amp;gt;exp_tasks pointer to NULL,
then CPU2 might dereference that NULL pointer.&lt;/p&gt;
&lt;p&gt;This commit therefore holds the rcu_node structure&amp;#39;s -&amp;gt;lock while
ac…&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;rcu: Protect rcu_print_task_exp_stall() -&amp;gt;exp_tasks access&lt;/p&gt;
&lt;p&gt;For kernels built with CONFIG_PREEMPT_RCU=y, the following scenario can
result in a NULL-pointer dereference:&lt;/p&gt;
&lt;p&gt;CPU1                                           CPU2
rcu_preempt_deferred_qs_irqrestore                rcu_print_task_exp_stall
  if (special.b.blocked)                            READ_ONCE(rnp-&amp;gt;exp_tasks) != NULL
    raw_spin_lock_rcu_node
    np = rcu_next_node_entry(t, rnp)
    if (&amp;amp;t-&amp;gt;rcu_node_entry == rnp-&amp;gt;exp_tasks)
      WRITE_ONCE(rnp-&amp;gt;exp_tasks, np)
      ....
      raw_spin_unlock_irqrestore_rcu_node
                                                    raw_spin_lock_irqsave_rcu_node
                                                    t = list_entry(rnp-&amp;gt;exp_tasks-&amp;gt;prev,
                                                        struct task_struct, rcu_node_entry)
                                                    (if rnp-&amp;gt;exp_tasks is NULL, this
                                                       will dereference a NULL pointer)&lt;/p&gt;
&lt;p&gt;The problem is that CPU2 accesses the rcu_node structure&amp;#39;s-&amp;gt;exp_tasks
field without holding the rcu_node structure&amp;#39;s -&amp;gt;lock and CPU2 did
not observe CPU1&amp;#39;s change to rcu_node structure&amp;#39;s -&amp;gt;exp_tasks in time.
Therefore, if CPU1 sets rcu_node structure&amp;#39;s-&amp;gt;exp_tasks pointer to NULL,
then CPU2 might dereference that NULL pointer.&lt;/p&gt;
&lt;p&gt;This commit therefore holds the rcu_node structure&amp;#39;s -&amp;gt;lock while
ac…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53419</guid>
    </item>
  </channel>
</rss>
