<?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-05T19:42:49.841804+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-99270</id>
    <title>CVE-2026-99270 — tcp: Fix potential UAF in reqsk_timer_handler().</title>
    <updated>2026-11-05T19:42:49.843079+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: Fix potential UAF in reqsk_timer_handler().</p>
<p>When TCP socket migration fails at inet_ehash_insert() in
reqsk_timer_handler(), we jump to the no_ownership: label
and free the new reqsk immediately with __reqsk_free().</p>
<p>Thus, we must stop the new reqsk's timer before jumping to the
label, but the timer might be missed since the cited commit,
resulting in UAF.</p>
<p>As we are in the original reqsk's timer context, we can safely
call timer_delete_sync() for the new reqsk.</p>
<p>Let's pass false to __inet_csk_reqsk_queue_drop() to stop
the new reqsk's timer.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99270"/>
  </entry>
</feed>
