PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-74696 Linux CVE debrief

A vulnerability in the Linux kernel's TCP Fast Open (TFO) implementation can allow a listener's TFO max_qlen configuration to be bypassed, potentially leading to an increased number of pending Fast Open requests. This issue arises when a listener with SO_REUSEPORT is migrated, and its pending TFO children are transferred to a surviving listener. The vulnerability's impact is primarily on system availability, as it can cause a denial of service.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-22
Original CVE updated
2026-10-16
Advisory published
2026-08-22
Advisory updated
2026-10-16

Who should care

System administrators and security teams responsible for Linux kernel-based systems, particularly those using TCP Fast Open, should assess their exposure and apply patches or mitigations as needed.

Why it matters

CVE-2026-74696 is a vulnerability in the Linux kernel's TCP Fast Open implementation that can lead to a denial of service. System administrators and security teams should assess their exposure, apply patches, and monitor system logs.

  • Denial of service (DoS) due to increased pending Fast Open requests.
  • Potential system slowdown or instability.
  • Need for additional monitoring and logging to detect potential attacks.
  • Verification of TFO max_qlen configuration and listener migration processes.

Technical summary

The Linux kernel's TCP Fast Open (TFO) implementation has a vulnerability that can cause a listener's TFO max_qlen configuration to be bypassed. This occurs when a listener with SO_REUSEPORT is migrated, and its pending TFO children are transferred to a surviving listener. The vulnerability can lead to an increased number of pending Fast Open requests, potentially causing a denial of service. System administrators and security teams should assess their exposure, apply patches, and monitor system logs. The CVE record and associated source item provide details on the vulnerability, including its description, affected versions, and references to relevant commits.

Defensive priority

Medium

Recommended defensive actions

  • Review and apply the available patches to ensure the TFO max_qlen configuration is enforced correctly.
  • Monitor system logs for potential denial-of-service (DoS) attempts.
  • Consider implementing additional network security measures to prevent exploitation.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and associated source item provide details on the vulnerability, including its description, affected versions, and references to relevant commits. However, there is limited information on potential exploits or attacks.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-74696 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-74696

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-74696 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-74696

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • tcp: fix TFO max_qlen accounting across reuseport migration

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/74xxx/CVE-2026-74696.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/e98f0d80b9cccb5f828425d2004f9686e7d1ae24

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b6247e0f96bd825ffb2005257f6177b5e642dee6

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/585fc5247d14939a561056aa2addd9b7c2b1f670

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/6e10ee56524a26b250229ad348637825646ddb88

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a66e869cf0c90c1e47ae75f72b6482acbfc808ff

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/d974618b2097453778389d385e3741629c40e0a3

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a0ab2ba83e35159d81cec830a92e885ecf8139be

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.