<?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 07:27:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21674 — net/mlx5e: Fix inversion dependency warning while enabling IPsec tunnel</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21674</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;net/mlx5e: Fix inversion dependency warning while enabling IPsec tunnel&lt;/p&gt;
&lt;p&gt;Attempt to enable IPsec packet offload in tunnel mode in debug kernel
generates the following kernel panic, which is happening due to two
issues:
1. In SA add section, the should be _bh() variant when marking SA mode.
2. There is not needed flush_workqueue in SA delete routine. It is not
needed as at this stage as it is removed from SADB and the running work
will be canceled later in SA free.&lt;/p&gt;
&lt;p&gt;=====================================================
 WARNING: SOFTIRQ-safe -&amp;gt; SOFTIRQ-unsafe lock order detected
 6.12.0+ #4 Not tainted
 -----------------------------------------------------
 charon/1337 [HC0[0]:SC0[4]:HE1:SE0] is trying to acquire:
 ffff88810f365020 (&amp;amp;xa-&amp;gt;xa_lock#24){+.+.}-{3:3}, at: mlx5e_xfrm_del_state+0xca/0x1e0 [mlx5_core]&lt;/p&gt;
&lt;p&gt;and this task is already holding:
 ffff88813e0f0d48 (&amp;amp;x-&amp;gt;lock){+.-.}-{3:3}, at: xfrm_state_delete+0x16/0x30
 which would create a new lock dependency:
  (&amp;amp;x-&amp;gt;lock){+.-.}-{3:3} -&amp;gt; (&amp;amp;xa-&amp;gt;xa_lock#24){+.+.}-{3:3}&lt;/p&gt;
&lt;p&gt;but this new dependency connects a SOFTIRQ-irq-safe lock:
  (&amp;amp;x-&amp;gt;lock){+.-.}-{3:3}&lt;/p&gt;
&lt;p&gt;... which became SOFTIRQ-irq-safe at:
   lock_acquire+0x1be/0x520
   _raw_spin_lock_bh+0x34/0x40
   xfrm_timer_handler+0x91/0xd70
   __hrtimer_run_queues+0x1dd/0xa60
   hrtimer_run_softirq+0x146/0x2e0
   handle_softirqs+0x266/0x860
   irq_exit_rcu+0x115/0x1a0
   sysvec_apic_timer_interrupt+0x6e/0x90
   asm_sys…&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;net/mlx5e: Fix inversion dependency warning while enabling IPsec tunnel&lt;/p&gt;
&lt;p&gt;Attempt to enable IPsec packet offload in tunnel mode in debug kernel
generates the following kernel panic, which is happening due to two
issues:
1. In SA add section, the should be _bh() variant when marking SA mode.
2. There is not needed flush_workqueue in SA delete routine. It is not
needed as at this stage as it is removed from SADB and the running work
will be canceled later in SA free.&lt;/p&gt;
&lt;p&gt;=====================================================
 WARNING: SOFTIRQ-safe -&amp;gt; SOFTIRQ-unsafe lock order detected
 6.12.0+ #4 Not tainted
 -----------------------------------------------------
 charon/1337 [HC0[0]:SC0[4]:HE1:SE0] is trying to acquire:
 ffff88810f365020 (&amp;amp;xa-&amp;gt;xa_lock#24){+.+.}-{3:3}, at: mlx5e_xfrm_del_state+0xca/0x1e0 [mlx5_core]&lt;/p&gt;
&lt;p&gt;and this task is already holding:
 ffff88813e0f0d48 (&amp;amp;x-&amp;gt;lock){+.-.}-{3:3}, at: xfrm_state_delete+0x16/0x30
 which would create a new lock dependency:
  (&amp;amp;x-&amp;gt;lock){+.-.}-{3:3} -&amp;gt; (&amp;amp;xa-&amp;gt;xa_lock#24){+.+.}-{3:3}&lt;/p&gt;
&lt;p&gt;but this new dependency connects a SOFTIRQ-irq-safe lock:
  (&amp;amp;x-&amp;gt;lock){+.-.}-{3:3}&lt;/p&gt;
&lt;p&gt;... which became SOFTIRQ-irq-safe at:
   lock_acquire+0x1be/0x520
   _raw_spin_lock_bh+0x34/0x40
   xfrm_timer_handler+0x91/0xd70
   __hrtimer_run_queues+0x1dd/0xa60
   hrtimer_run_softirq+0x146/0x2e0
   handle_softirqs+0x266/0x860
   irq_exit_rcu+0x115/0x1a0
   sysvec_apic_timer_interrupt+0x6e/0x90
   asm_sys…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21674</guid>
    </item>
  </channel>
</rss>
