<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-16T06:13:05.984371+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-99285</id>
    <title>fkie_cve-2026-99285</title>
    <updated>2026-11-16T06:13:05.993987+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>netfilter: nft_byteorder: remove multi-register support</p>
<p>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:</p>
<p>for (i = ...
      src64 = nft_reg_load64(&amp;src[i]);
                             ~~~~~ u32 *src
      nft_reg_store64(&amp;dst64[i],</p>
<p>Remove the multi-register support, it has other issues as well:</p>
<p>Pablo points out that commit
caf3ef7468f7 ("netfilter: nf_tables: prevent OOB access in nft_byteorder_eval")
alters semantics: before the loop operated on registers, i.e.
 for ( ... )
   dst32[i] = htons((u16)src32[i])</p>
<p>.. 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.</p>
<p>Multi-convert of u32 has one theoretical application:</p>
<p>ct mark . meta mark . tcp dport @intervalset</p>
<p>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).</p>
<p>nftables emits this:
 [ meta load mark =&gt; reg 1 ]
 [ byteorder reg 1 = hton(reg 1, 4, 4) ]
 [ ct load mark =&gt; reg 9 ]
 [ byteorder reg 9 = hton(reg 9, 4, 4) ]
 ...</p>
<p>I.e. two separate calls.  Theoretically it could be changed to do:
 [ meta load mark =&gt; reg 1 ]
 [ ct load mark =&gt; reg 9 ]
 [ byteorder reg 1 = htonl(reg 1, 4, 8) ]
 ...</p>
<p>But then all it would take to change the set…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99285"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-vmhm-3cg3-fm3j</id>
    <title>GHSA-vmhm-3cg3-fm3j</title>
    <updated>2026-11-16T06:13:05.994199+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>netfilter: nft_byteorder: remove multi-register support</p>
<p>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:</p>
<p>for (i = ...
      src64 = nft_reg_load64(&amp;src[i]);
                             ~~~~~ u32 *src
      nft_reg_store64(&amp;dst64[i],</p>
<p>Remove the multi-register support, it has other issues as well:</p>
<p>Pablo points out that commit
caf3ef7468f7 ("netfilter: nf_tables: prevent OOB access in nft_byteorder_eval")
alters semantics: before the loop operated on registers, i.e.
 for ( ... )
   dst32[i] = htons((u16)src32[i])</p>
<p>.. 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.</p>
<p>Multi-convert of u32 has one theoretical application:</p>
<p>ct mark . meta mark . tcp dport @intervalset</p>
<p>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).</p>
<p>nftables emits this:
 [ meta load mark =&gt; reg 1 ]
 [ byteorder reg 1 = hton(reg 1, 4, 4) ]
 [ ct load mark =&gt; reg 9 ]
 [ byteorder reg 9 = hton(reg 9, 4, 4) ]
 ...</p>
<p>I.e. two separate calls.  Theoretically it could be changed to do:
 [ meta load mark =&gt; reg 1 ]
 [ ct load mark =&gt; reg 9 ]
 [ byteorder reg 1 = htonl(reg 1, 4, 8) ]
 ...</p>
<p>But then all it would take to change the set…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-vmhm-3cg3-fm3j"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/msrc_cve-2026-99285</id>
    <title>msrc_CVE-2026-99285 — netfilter: nft_byteorder: remove multi-register support</title>
    <updated>2026-11-16T06:13:05.994268+00:00</updated>
    <content>msrc_CVE-2026-99285</content>
    <link href="https://db.gcve.eu/vuln/msrc_cve-2026-99285"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2026-99285</id>
    <title>UBUNTU-CVE-2026-99285</title>
    <updated>2026-11-16T06:13:05.994308+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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;src[i]);                              ~~~~~ u32 *src       nft_reg_store64(&amp;dst64[i], Remove the multi-register support, it has other issues as well: Pablo points out that commit caf3ef7468f7 ("netfilter: nf_tables: prevent OOB access in nft_byteorder_eval") 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 =&gt; reg 1 ]  [ byteorder reg 1 = hton(reg 1, 4, 4) ]  [ ct load mark =&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 =&gt; reg 1 ]  [ ct load mark =&gt; reg 9 ]  [ byteorder reg 1 = htonl(reg 1, 4, 8) ]  ... But then all it would take to change the set to meta mar…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2026-99285"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2026-4461</id>
    <title>WID-SEC-W-2026-4461 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-11-16T06:13:05.994720+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/wid-sec-w-2026-4461"/>
  </entry>
</feed>
