<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T21:33:12.835368+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2022-49325</id>
    <title>CVE-2022-49325 — tcp: add accessors to read/set tp-&gt;snd_cwnd</title>
    <updated>2026-10-03T21:33:12.855633+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: add accessors to read/set tp-&gt;snd_cwnd</p>
<p>We had various bugs over the years with code
breaking the assumption that tp-&gt;snd_cwnd is greater
than zero.</p>
<p>Lately, syzbot reported the WARN_ON_ONCE(!tp-&gt;prior_cwnd) added
in commit 8b8a321ff72c ("tcp: fix zero cwnd in tcp_cwnd_reduction")
can trigger, and without a repro we would have to spend
considerable time finding the bug.</p>
<p>Instead of complaining too late, we want to catch where
and when tp-&gt;snd_cwnd is set to an illegal value.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-49325"/>
  </entry>
</feed>
