From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74696: tcp: fix TFO max_qlen accounting across reuseport migration
Date: Sat, 22 Aug 2026 17:33:00 +0200 [thread overview]
Message-ID: <2026082234-CVE-2026-74696-3187@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
tcp: fix TFO max_qlen accounting across reuseport migration
A listener's TCP_FASTOPEN max_qlen stops being accurate and lets through
far more pending Fast Open requests than it was configured for.
This only shows up with SO_REUSEPORT listener migration, where closing a
listener hands its still-pending TFO children over to a surviving one.
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's qlen drifts negative and its
limit no longer binds.
Charge the new listener during migration, like reqsk_queue_migrated()
already does for queue->young and queue->qlen.
The Linux kernel CVE team has assigned CVE-2026-74696 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.14 with commit 54b92e84193749c9968aff2dd46e3b0f42643e18 and fixed in 5.15.216 with commit e98f0d80b9cccb5f828425d2004f9686e7d1ae24
Issue introduced in 5.14 with commit 54b92e84193749c9968aff2dd46e3b0f42643e18 and fixed in 6.1.183 with commit b6247e0f96bd825ffb2005257f6177b5e642dee6
Issue introduced in 5.14 with commit 54b92e84193749c9968aff2dd46e3b0f42643e18 and fixed in 6.6.152 with commit 585fc5247d14939a561056aa2addd9b7c2b1f670
Issue introduced in 5.14 with commit 54b92e84193749c9968aff2dd46e3b0f42643e18 and fixed in 6.12.104 with commit 6e10ee56524a26b250229ad348637825646ddb88
Issue introduced in 5.14 with commit 54b92e84193749c9968aff2dd46e3b0f42643e18 and fixed in 6.18.45 with commit a66e869cf0c90c1e47ae75f72b6482acbfc808ff
Issue introduced in 5.14 with commit 54b92e84193749c9968aff2dd46e3b0f42643e18 and fixed in 7.1.9 with commit d974618b2097453778389d385e3741629c40e0a3
Issue introduced in 5.14 with commit 54b92e84193749c9968aff2dd46e3b0f42643e18 and fixed in 7.2 with commit a0ab2ba83e35159d81cec830a92e885ecf8139be
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-74696
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
net/ipv4/inet_connection_sock.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/e98f0d80b9cccb5f828425d2004f9686e7d1ae24
https://git.kernel.org/stable/c/b6247e0f96bd825ffb2005257f6177b5e642dee6
https://git.kernel.org/stable/c/585fc5247d14939a561056aa2addd9b7c2b1f670
https://git.kernel.org/stable/c/6e10ee56524a26b250229ad348637825646ddb88
https://git.kernel.org/stable/c/a66e869cf0c90c1e47ae75f72b6482acbfc808ff
https://git.kernel.org/stable/c/d974618b2097453778389d385e3741629c40e0a3
https://git.kernel.org/stable/c/a0ab2ba83e35159d81cec830a92e885ecf8139be
reply other threads:[~2026-08-22 15:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026082234-CVE-2026-74696-3187@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.