CVE-2026-74696

tcp: fix TFO max_qlen accounting across reuseport migration

HIGH
7.5
CVSS Score
Published: August 22, 2026 at 03:32 PM UTC
Updated: October 16, 2026 at 08:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.1454b92e84193749c9968aff2dd46e3b0f42643e18
Vendor states this is fixed in 585fc5247d14939a561056aa2addd9b7c2b1f670 (fixed)
Vendor states this is fixed in 6e10ee56524a26b250229ad348637825646ddb88 (fixed)
Vendor states this is fixed in a0ab2ba83e35159d81cec830a92e885ecf8139be (fixed)
Vendor states this is fixed in a66e869cf0c90c1e47ae75f72b6482acbfc808ff (fixed)
Vendor states this is fixed in b6247e0f96bd825ffb2005257f6177b5e642dee6 (fixed)
Vendor states this is fixed in d974618b2097453778389d385e3741629c40e0a3 (fixed)
Vendor states this is fixed in e98f0d80b9cccb5f828425d2004f9686e7d1ae24 (fixed)
Vendor states this is fixed in 5.14 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.104 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Vendor states this is fixed in 6.6.152 (unaffected)
Vendor states this is fixed in 7.1.9 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card