<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T10:46:23.275306+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-23274</id>
    <title>CVE-2026-23274 — netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels</title>
    <updated>2026-09-29T10:46:23.293124+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels</p>
<p>IDLETIMER revision 0 rules reuse existing timers by label and always call
mod_timer() on timer-&gt;timer.</p>
<p>If the label was created first by revision 1 with XT_IDLETIMER_ALARM,
the object uses alarm timer semantics and timer-&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.</p>
<p>Fix this by rejecting revision 0 rule insertion when an existing timer with
the same label is of ALARM type.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-23274"/>
  </entry>
</feed>
