<?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>Mon, 16 Nov 2026 06:13:06 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99285</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99285</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nft_byteorder: remove multi-register support&lt;/p&gt;
&lt;p&gt;64bit byteorder conversion is broken when several registers need to be
converted because the source register array advances in steps for 4 bytes
instead of 8:&lt;/p&gt;
&lt;p&gt;for (i = ...
      src64 = nft_reg_load64(&amp;amp;src[i]);
                             ~~~~~ u32 *src
      nft_reg_store64(&amp;amp;dst64[i],&lt;/p&gt;
&lt;p&gt;Remove the multi-register support, it has other issues as well:&lt;/p&gt;
&lt;p&gt;Pablo points out that commit
caf3ef7468f7 (&amp;#34;netfilter: nf_tables: prevent OOB access in nft_byteorder_eval&amp;#34;)
alters semantics: before the loop operated on registers, i.e.
 for ( ... )
   dst32[i] = htons((u16)src32[i])&lt;/p&gt;
&lt;p&gt;.. but after the patch it will operate on bytes, which makes this
 useless to convert e.g. concatenations, which store each compound
 in its own register.&lt;/p&gt;
&lt;p&gt;Multi-convert of u32 has one theoretical application:&lt;/p&gt;
&lt;p&gt;ct mark . meta mark . tcp dport @intervalset&lt;/p&gt;
&lt;p&gt;Because ct mark and meta mark are host byte order, use with
intervals has to convert the byteorder for ct/meta mark value
to network byte order (bigendian).&lt;/p&gt;
&lt;p&gt;nftables emits this:
 [ meta load mark =&amp;gt; reg 1 ]
 [ byteorder reg 1 = hton(reg 1, 4, 4) ]
 [ ct load mark =&amp;gt; reg 9 ]
 [ byteorder reg 9 = hton(reg 9, 4, 4) ]
 ...&lt;/p&gt;
&lt;p&gt;I.e. two separate calls.  Theoretically it could be changed to do:
 [ meta load mark =&amp;gt; reg 1 ]
 [ ct load mark =&amp;gt; reg 9 ]
 [ byteorder reg 1 = htonl(reg 1, 4, 8) ]
 ...&lt;/p&gt;
&lt;p&gt;But then all it would take to change the set…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nft_byteorder: remove multi-register support&lt;/p&gt;
&lt;p&gt;64bit byteorder conversion is broken when several registers need to be
converted because the source register array advances in steps for 4 bytes
instead of 8:&lt;/p&gt;
&lt;p&gt;for (i = ...
      src64 = nft_reg_load64(&amp;amp;src[i]);
                             ~~~~~ u32 *src
      nft_reg_store64(&amp;amp;dst64[i],&lt;/p&gt;
&lt;p&gt;Remove the multi-register support, it has other issues as well:&lt;/p&gt;
&lt;p&gt;Pablo points out that commit
caf3ef7468f7 (&amp;#34;netfilter: nf_tables: prevent OOB access in nft_byteorder_eval&amp;#34;)
alters semantics: before the loop operated on registers, i.e.
 for ( ... )
   dst32[i] = htons((u16)src32[i])&lt;/p&gt;
&lt;p&gt;.. but after the patch it will operate on bytes, which makes this
 useless to convert e.g. concatenations, which store each compound
 in its own register.&lt;/p&gt;
&lt;p&gt;Multi-convert of u32 has one theoretical application:&lt;/p&gt;
&lt;p&gt;ct mark . meta mark . tcp dport @intervalset&lt;/p&gt;
&lt;p&gt;Because ct mark and meta mark are host byte order, use with
intervals has to convert the byteorder for ct/meta mark value
to network byte order (bigendian).&lt;/p&gt;
&lt;p&gt;nftables emits this:
 [ meta load mark =&amp;gt; reg 1 ]
 [ byteorder reg 1 = hton(reg 1, 4, 4) ]
 [ ct load mark =&amp;gt; reg 9 ]
 [ byteorder reg 9 = hton(reg 9, 4, 4) ]
 ...&lt;/p&gt;
&lt;p&gt;I.e. two separate calls.  Theoretically it could be changed to do:
 [ meta load mark =&amp;gt; reg 1 ]
 [ ct load mark =&amp;gt; reg 9 ]
 [ byteorder reg 1 = htonl(reg 1, 4, 8) ]
 ...&lt;/p&gt;
&lt;p&gt;But then all it would take to change the set…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99285</guid>
    </item>
    <item>
      <title>GHSA-vmhm-3cg3-fm3j</title>
      <link>https://db.gcve.eu/vuln/ghsa-vmhm-3cg3-fm3j</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nft_byteorder: remove multi-register support&lt;/p&gt;
&lt;p&gt;64bit byteorder conversion is broken when several registers need to be
converted because the source register array advances in steps for 4 bytes
instead of 8:&lt;/p&gt;
&lt;p&gt;for (i = ...
      src64 = nft_reg_load64(&amp;amp;src[i]);
                             ~~~~~ u32 *src
      nft_reg_store64(&amp;amp;dst64[i],&lt;/p&gt;
&lt;p&gt;Remove the multi-register support, it has other issues as well:&lt;/p&gt;
&lt;p&gt;Pablo points out that commit
caf3ef7468f7 (&amp;#34;netfilter: nf_tables: prevent OOB access in nft_byteorder_eval&amp;#34;)
alters semantics: before the loop operated on registers, i.e.
 for ( ... )
   dst32[i] = htons((u16)src32[i])&lt;/p&gt;
&lt;p&gt;.. but after the patch it will operate on bytes, which makes this
 useless to convert e.g. concatenations, which store each compound
 in its own register.&lt;/p&gt;
&lt;p&gt;Multi-convert of u32 has one theoretical application:&lt;/p&gt;
&lt;p&gt;ct mark . meta mark . tcp dport @intervalset&lt;/p&gt;
&lt;p&gt;Because ct mark and meta mark are host byte order, use with
intervals has to convert the byteorder for ct/meta mark value
to network byte order (bigendian).&lt;/p&gt;
&lt;p&gt;nftables emits this:
 [ meta load mark =&amp;gt; reg 1 ]
 [ byteorder reg 1 = hton(reg 1, 4, 4) ]
 [ ct load mark =&amp;gt; reg 9 ]
 [ byteorder reg 9 = hton(reg 9, 4, 4) ]
 ...&lt;/p&gt;
&lt;p&gt;I.e. two separate calls.  Theoretically it could be changed to do:
 [ meta load mark =&amp;gt; reg 1 ]
 [ ct load mark =&amp;gt; reg 9 ]
 [ byteorder reg 1 = htonl(reg 1, 4, 8) ]
 ...&lt;/p&gt;
&lt;p&gt;But then all it would take to change the set…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nft_byteorder: remove multi-register support&lt;/p&gt;
&lt;p&gt;64bit byteorder conversion is broken when several registers need to be
converted because the source register array advances in steps for 4 bytes
instead of 8:&lt;/p&gt;
&lt;p&gt;for (i = ...
      src64 = nft_reg_load64(&amp;amp;src[i]);
                             ~~~~~ u32 *src
      nft_reg_store64(&amp;amp;dst64[i],&lt;/p&gt;
&lt;p&gt;Remove the multi-register support, it has other issues as well:&lt;/p&gt;
&lt;p&gt;Pablo points out that commit
caf3ef7468f7 (&amp;#34;netfilter: nf_tables: prevent OOB access in nft_byteorder_eval&amp;#34;)
alters semantics: before the loop operated on registers, i.e.
 for ( ... )
   dst32[i] = htons((u16)src32[i])&lt;/p&gt;
&lt;p&gt;.. but after the patch it will operate on bytes, which makes this
 useless to convert e.g. concatenations, which store each compound
 in its own register.&lt;/p&gt;
&lt;p&gt;Multi-convert of u32 has one theoretical application:&lt;/p&gt;
&lt;p&gt;ct mark . meta mark . tcp dport @intervalset&lt;/p&gt;
&lt;p&gt;Because ct mark and meta mark are host byte order, use with
intervals has to convert the byteorder for ct/meta mark value
to network byte order (bigendian).&lt;/p&gt;
&lt;p&gt;nftables emits this:
 [ meta load mark =&amp;gt; reg 1 ]
 [ byteorder reg 1 = hton(reg 1, 4, 4) ]
 [ ct load mark =&amp;gt; reg 9 ]
 [ byteorder reg 9 = hton(reg 9, 4, 4) ]
 ...&lt;/p&gt;
&lt;p&gt;I.e. two separate calls.  Theoretically it could be changed to do:
 [ meta load mark =&amp;gt; reg 1 ]
 [ ct load mark =&amp;gt; reg 9 ]
 [ byteorder reg 1 = htonl(reg 1, 4, 8) ]
 ...&lt;/p&gt;
&lt;p&gt;But then all it would take to change the set…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-vmhm-3cg3-fm3j</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99285 — netfilter: nft_byteorder: remove multi-register support</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-99285</link>
      <description>msrc_CVE-2026-99285</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-99285</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-99285</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-99285</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 258 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_byteorder: remove multi-register support 64bit byteorder conversion is broken when several registers need to be converted because the source register array advances in steps for 4 bytes instead of 8:   for (i = ...       src64 = nft_reg_load64(&amp;amp;src[i]);                              ~~~~~ u32 *src       nft_reg_store64(&amp;amp;dst64[i], Remove the multi-register support, it has other issues as well: Pablo points out that commit caf3ef7468f7 (&amp;#34;netfilter: nf_tables: prevent OOB access in nft_byteorder_eval&amp;#34;) alters semantics: before the loop operated on registers, i.e.  for ( ... )    dst32[i] = htons((u16)src32[i])  .. but after the patch it will operate on bytes, which makes this  useless to convert e.g. concatenations, which store each compound  in its own register. Multi-convert of u32 has one theoretical application: ct mark . meta mark . tcp dport @intervalset Because ct mark and meta mark are host byte order, use with intervals has to convert the byteorder for ct/meta mark value to network byte order (bigendian). nftables emits this:  [ meta load mark =&amp;gt; reg 1 ]  [ byteorder reg 1 = hton(reg 1, 4, 4) ]  [ ct load mark =&amp;gt; reg 9 ]  [ byteorder reg 9 = hton(reg 9, 4, 4) ]  ... I.e. two separate calls.  Theoretically it could be changed to do:  [ meta load mark =&amp;gt; reg 1 ]  [ ct load mark =&amp;gt; reg 9 ]  [ byteorder reg 1 = htonl(reg 1, 4, 8) ]  ... But then all it would take to change the set to meta mar…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 258 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_byteorder: remove multi-register support 64bit byteorder conversion is broken when several registers need to be converted because the source register array advances in steps for 4 bytes instead of 8:   for (i = ...       src64 = nft_reg_load64(&amp;amp;src[i]);                              ~~~~~ u32 *src       nft_reg_store64(&amp;amp;dst64[i], Remove the multi-register support, it has other issues as well: Pablo points out that commit caf3ef7468f7 (&amp;#34;netfilter: nf_tables: prevent OOB access in nft_byteorder_eval&amp;#34;) alters semantics: before the loop operated on registers, i.e.  for ( ... )    dst32[i] = htons((u16)src32[i])  .. but after the patch it will operate on bytes, which makes this  useless to convert e.g. concatenations, which store each compound  in its own register. Multi-convert of u32 has one theoretical application: ct mark . meta mark . tcp dport @intervalset Because ct mark and meta mark are host byte order, use with intervals has to convert the byteorder for ct/meta mark value to network byte order (bigendian). nftables emits this:  [ meta load mark =&amp;gt; reg 1 ]  [ byteorder reg 1 = hton(reg 1, 4, 4) ]  [ ct load mark =&amp;gt; reg 9 ]  [ byteorder reg 9 = hton(reg 9, 4, 4) ]  ... I.e. two separate calls.  Theoretically it could be changed to do:  [ meta load mark =&amp;gt; reg 1 ]  [ ct load mark =&amp;gt; reg 9 ]  [ byteorder reg 1 = htonl(reg 1, 4, 8) ]  ... But then all it would take to change the set to meta mar…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-99285</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4461 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4461</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu verursachen oder nicht näher spezifizierte Auswirkungen auszulösen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu verursachen oder nicht näher spezifizierte Auswirkungen auszulösen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4461</guid>
    </item>
  </channel>
</rss>
