<?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>Sun, 01 Nov 2026 21:45:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98794 — ipvs: filter some flags received in the backup server</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98794</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;ipvs: filter some flags received in the backup server&lt;/p&gt;
&lt;p&gt;While the IPVS SYNC protocol is not secure by design
we can still protect the backup server from messages that
can wreak havoc.&lt;/p&gt;
&lt;p&gt;This commit addresses problems from received connection flags
or their combinations. We now drop messages as follows:&lt;/p&gt;
&lt;p&gt;1. the NO_CPORT+TEMPLATE combination allows lookups for normal
connections to hit template which can break in many ways.
While the master does not sync connections with NO_CPORT flag,
i.e. before they are established, we still accept NO_CPORT
without TEMPLATE.&lt;/p&gt;
&lt;p&gt;2. ONE_PACKET: it is not sent by master, so we do not
expect it in backup. Before now it was ignored by
IP_VS_CONN_F_BACKUP_MASK for protocol v1 while protocol
v0 created connections that are not hashed and dropped
immediately. Better to apply the IP_VS_CONN_F_BACKUP_MASK
also to the flags from v0 messages for consistency with v1.&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;ipvs: filter some flags received in the backup server&lt;/p&gt;
&lt;p&gt;While the IPVS SYNC protocol is not secure by design
we can still protect the backup server from messages that
can wreak havoc.&lt;/p&gt;
&lt;p&gt;This commit addresses problems from received connection flags
or their combinations. We now drop messages as follows:&lt;/p&gt;
&lt;p&gt;1. the NO_CPORT+TEMPLATE combination allows lookups for normal
connections to hit template which can break in many ways.
While the master does not sync connections with NO_CPORT flag,
i.e. before they are established, we still accept NO_CPORT
without TEMPLATE.&lt;/p&gt;
&lt;p&gt;2. ONE_PACKET: it is not sent by master, so we do not
expect it in backup. Before now it was ignored by
IP_VS_CONN_F_BACKUP_MASK for protocol v1 while protocol
v0 created connections that are not hashed and dropped
immediately. Better to apply the IP_VS_CONN_F_BACKUP_MASK
also to the flags from v0 messages for consistency with v1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98794</guid>
    </item>
  </channel>
</rss>
