https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 22:58:23 +0000 https://vulnerability.circl.lu/vuln/cve-2026-74696 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tcp: fix TFO max_qlen accounting across reuseport migration</p> <p>A listener&#39;s TCP_FASTOPEN max_qlen stops being accurate and lets through far more pending Fast Open requests than it was configured for.</p> <p>This only shows up with SO_REUSEPORT listener migration, where closing a listener hands its still-pending TFO children over to a surviving one.</p> <p>fastopenq.qlen is charged in tcp_fastopen_create_child() when the child is created and uncharged in reqsk_fastopen_remove() when the handshake completes. The uncharge follows rsk_listener of the request the child points at, and inet_reqsk_clone() has repointed the child at a new request owned by the new listener, so the ++ and the -- land on two different sockets. The new listener&#39;s qlen drifts negative and its limit no longer binds.</p> <p>Charge the new listener during migration, like reqsk_queue_migrated() already does for queue-&gt;young and queue-&gt;qlen.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tcp: fix TFO max_qlen accounting across reuseport migration</p> <p>A listener&#39;s TCP_FASTOPEN max_qlen stops being accurate and lets through far more pending Fast Open requests than it was configured for.</p> <p>This only shows up with SO_REUSEPORT listener migration, where closing a listener hands its still-pending TFO children over to a surviving one.</p> <p>fastopenq.qlen is charged in tcp_fastopen_create_child() when the child is created and uncharged in reqsk_fastopen_remove() when the handshake completes. The uncharge follows rsk_listener of the request the child points at, and inet_reqsk_clone() has repointed the child at a new request owned by the new listener, so the ++ and the -- land on two different sockets. The new listener&#39;s qlen drifts negative and its limit no longer binds.</p> <p>Charge the new listener during migration, like reqsk_queue_migrated() already does for queue-&gt;young and queue-&gt;qlen.</p> https://vulnerability.circl.lu/vuln/cve-2026-74696