<?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-10-01T12:34:15.010128+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-23247</id>
    <title>CVE-2026-23247 — tcp: secure_seq: add back ports to TS offset</title>
    <updated>2026-10-01T12:34:15.029845+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>tcp: secure_seq: add back ports to TS offset</p>
<p>This reverts 28ee1b746f49 ("secure_seq: downgrade to per-host timestamp offsets")</p>
<p>tcp_tw_recycle went away in 2017.</p>
<p>Zhouyan Deng reported off-path TCP source port leakage via
SYN cookie side-channel that can be fixed in multiple ways.</p>
<p>One of them is to bring back TCP ports in TS offset randomization.</p>
<p>As a bonus, we perform a single siphash() computation
to provide both an ISN and a TS offset.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-23247"/>
  </entry>
</feed>
