<?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:34:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74624 — netfilter: nf_conntrack: defer invalid log until after unlock</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74624</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;netfilter: nf_conntrack: defer invalid log until after unlock&lt;/p&gt;
&lt;p&gt;TCP and SCTP conntrack paths can emit invalid-packet logs while ct-&amp;gt;lock
is still held.&lt;/p&gt;
&lt;p&gt;When invalid logging is routed to nfnetlink_log and conntrack export is
enabled, the log path can re-enter conntrack netlink glue and dump the
same conntrack again. Protocol attribute dumping may take ct-&amp;gt;lock, so
logging while holding that lock can deadlock.&lt;/p&gt;
&lt;p&gt;Defer the TCP invalid logs by storing only the minimal log context while
ct-&amp;gt;lock is held and emitting the log after unlocking. Also make the TCP
timeout-lowering invalid path return whether a log is needed, then emit
that log after unlocking.&lt;/p&gt;
&lt;p&gt;Do the same for the SCTP invalid state-transition log that can be reached
while ct-&amp;gt;lock is held.&lt;/p&gt;
&lt;p&gt;Add a lockdep assertion to nf_ct_l4proto_log_invalid() so future callers
that log invalid conntracks while holding ct-&amp;gt;lock are caught outside TCP
and SCTP as well.&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;netfilter: nf_conntrack: defer invalid log until after unlock&lt;/p&gt;
&lt;p&gt;TCP and SCTP conntrack paths can emit invalid-packet logs while ct-&amp;gt;lock
is still held.&lt;/p&gt;
&lt;p&gt;When invalid logging is routed to nfnetlink_log and conntrack export is
enabled, the log path can re-enter conntrack netlink glue and dump the
same conntrack again. Protocol attribute dumping may take ct-&amp;gt;lock, so
logging while holding that lock can deadlock.&lt;/p&gt;
&lt;p&gt;Defer the TCP invalid logs by storing only the minimal log context while
ct-&amp;gt;lock is held and emitting the log after unlocking. Also make the TCP
timeout-lowering invalid path return whether a log is needed, then emit
that log after unlocking.&lt;/p&gt;
&lt;p&gt;Do the same for the SCTP invalid state-transition log that can be reached
while ct-&amp;gt;lock is held.&lt;/p&gt;
&lt;p&gt;Add a lockdep assertion to nf_ct_l4proto_log_invalid() so future callers
that log invalid conntracks while holding ct-&amp;gt;lock are caught outside TCP
and SCTP as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74624</guid>
    </item>
  </channel>
</rss>
