<?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>Thu, 01 Oct 2026 13:55:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-40983 — tipc: force a dst refcount before doing decryption</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-40983</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;tipc: force a dst refcount before doing decryption&lt;/p&gt;
&lt;p&gt;As it says in commit 3bc07321ccc2 (&amp;#34;xfrm: Force a dst refcount before
entering the xfrm type handlers&amp;#34;):&lt;/p&gt;
&lt;p&gt;&amp;#34;Crypto requests might return asynchronous. In this case we leave the
 rcu protected region, so force a refcount on the skb&amp;#39;s destination
 entry before we enter the xfrm type input/output handlers.&amp;#34;&lt;/p&gt;
&lt;p&gt;On TIPC decryption path it has the same problem, and skb_dst_force()
should be called before doing decryption to avoid a possible crash.&lt;/p&gt;
&lt;p&gt;Shuang reported this issue when this warning is triggered:&lt;/p&gt;
&lt;p&gt;[] WARNING: include/net/dst.h:337 tipc_sk_rcv+0x1055/0x1ea0 [tipc]
  [] Kdump: loaded Tainted: G W --------- - - 4.18.0-496.el8.x86_64+debug
  [] Workqueue: crypto cryptd_queue_worker
  [] RIP: 0010:tipc_sk_rcv+0x1055/0x1ea0 [tipc]
  [] Call Trace:
  [] tipc_sk_mcast_rcv+0x548/0xea0 [tipc]
  [] tipc_rcv+0xcf5/0x1060 [tipc]
  [] tipc_aead_decrypt_done+0x215/0x2e0 [tipc]
  [] cryptd_aead_crypt+0xdb/0x190
  [] cryptd_queue_worker+0xed/0x190
  [] process_one_work+0x93d/0x17e0&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;tipc: force a dst refcount before doing decryption&lt;/p&gt;
&lt;p&gt;As it says in commit 3bc07321ccc2 (&amp;#34;xfrm: Force a dst refcount before
entering the xfrm type handlers&amp;#34;):&lt;/p&gt;
&lt;p&gt;&amp;#34;Crypto requests might return asynchronous. In this case we leave the
 rcu protected region, so force a refcount on the skb&amp;#39;s destination
 entry before we enter the xfrm type input/output handlers.&amp;#34;&lt;/p&gt;
&lt;p&gt;On TIPC decryption path it has the same problem, and skb_dst_force()
should be called before doing decryption to avoid a possible crash.&lt;/p&gt;
&lt;p&gt;Shuang reported this issue when this warning is triggered:&lt;/p&gt;
&lt;p&gt;[] WARNING: include/net/dst.h:337 tipc_sk_rcv+0x1055/0x1ea0 [tipc]
  [] Kdump: loaded Tainted: G W --------- - - 4.18.0-496.el8.x86_64+debug
  [] Workqueue: crypto cryptd_queue_worker
  [] RIP: 0010:tipc_sk_rcv+0x1055/0x1ea0 [tipc]
  [] Call Trace:
  [] tipc_sk_mcast_rcv+0x548/0xea0 [tipc]
  [] tipc_rcv+0xcf5/0x1060 [tipc]
  [] tipc_aead_decrypt_done+0x215/0x2e0 [tipc]
  [] cryptd_aead_crypt+0xdb/0x190
  [] cryptd_queue_worker+0xed/0x190
  [] process_one_work+0x93d/0x17e0&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-40983</guid>
    </item>
  </channel>
</rss>
