<?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-20T21:21:25.185646+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/cve-2026-99402</id>
    <title>CVE-2026-99402 — netfilter: nft_payload: restrict checksum offsets to known values</title>
    <updated>2026-11-20T21:21:25.188523+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>netfilter: nft_payload: restrict checksum offsets to known values</p>
<p>We need to prevent userspace from corrupting e.g. tcp-&gt;doff, because
many locations in conntrack and conntrack helpers rely on
nf_conntrack_in() having validated the packet headers.
nft_payload allows to alter headers later which invalidates this
assumption.</p>
<p>The 'Fixes' commit restricts writes to safe fields, but there is
another side channel: the checksum location.</p>
<p>Restrict this too.  Reported via sashiko/gemini.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99402"/>
  </entry>
</feed>
