<?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://db.gcve.eu</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>Sat, 03 Oct 2026 01:48:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53218 — netfilter: nft_exthdr: fix register tracking for F_PRESENT flag</title>
      <link>https://db.gcve.eu/vuln/cve-2026-53218</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: nft_exthdr: fix register tracking for F_PRESENT flag&lt;/p&gt;
&lt;p&gt;nft_exthdr_init() passes user-controlled priv-&amp;gt;len to
nft_parse_register_store(), which marks that many bytes in the
register bitmap as initialized.  However, when NFT_EXTHDR_F_PRESENT
is set, the eval paths write only 1 byte (nft_reg_store8) or
4 bytes (*dest = 0 on TCP/DCCP error path).  When len &amp;gt; 4,
registers beyond the first are never written, retaining
uninitialized stack data from nft_regs.&lt;/p&gt;
&lt;p&gt;Bail out if userspace requests too much data when F_PRESENT is set.&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: nft_exthdr: fix register tracking for F_PRESENT flag&lt;/p&gt;
&lt;p&gt;nft_exthdr_init() passes user-controlled priv-&amp;gt;len to
nft_parse_register_store(), which marks that many bytes in the
register bitmap as initialized.  However, when NFT_EXTHDR_F_PRESENT
is set, the eval paths write only 1 byte (nft_reg_store8) or
4 bytes (*dest = 0 on TCP/DCCP error path).  When len &amp;gt; 4,
registers beyond the first are never written, retaining
uninitialized stack data from nft_regs.&lt;/p&gt;
&lt;p&gt;Bail out if userspace requests too much data when F_PRESENT is set.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-53218</guid>
    </item>
  </channel>
</rss>
