<?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 13:39:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23274 — netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23274</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels&lt;/p&gt;
&lt;p&gt;IDLETIMER revision 0 rules reuse existing timers by label and always call
mod_timer() on timer-&amp;gt;timer.&lt;/p&gt;
&lt;p&gt;If the label was created first by revision 1 with XT_IDLETIMER_ALARM,
the object uses alarm timer semantics and timer-&amp;gt;timer is never initialized.
Reusing that object from revision 0 causes mod_timer() on an uninitialized
timer_list, triggering debugobjects warnings and possible panic when
panic_on_warn=1.&lt;/p&gt;
&lt;p&gt;Fix this by rejecting revision 0 rule insertion when an existing timer with
the same label is of ALARM type.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels&lt;/p&gt;
&lt;p&gt;IDLETIMER revision 0 rules reuse existing timers by label and always call
mod_timer() on timer-&amp;gt;timer.&lt;/p&gt;
&lt;p&gt;If the label was created first by revision 1 with XT_IDLETIMER_ALARM,
the object uses alarm timer semantics and timer-&amp;gt;timer is never initialized.
Reusing that object from revision 0 causes mod_timer() on an uninitialized
timer_list, triggering debugobjects warnings and possible panic when
panic_on_warn=1.&lt;/p&gt;
&lt;p&gt;Fix this by rejecting revision 0 rule insertion when an existing timer with
the same label is of ALARM type.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23274</guid>
    </item>
  </channel>
</rss>
