CVE-2026-23321 Linux CVE debrief

Who should care

Linux kernel users and administrators should be aware of this vulnerability, especially those using kernel versions 6.1.106 to 6.1.167, 6.6.46 to 6.6.130, 6.10.5 to 6.11, 6.11.1 to 6.12.78, 6.13 to 6.18.17, 6.19 to 6.19.7, and 7.0 rc1 to rc7. They should verify their kernel versions and apply patches or updates to mitigate the vulnerability.

Technical summary

The vulnerability is caused by a combination of actions that can generate a warning in the MPTCP protocol. The actions that can trigger the warning are: setting the MPTCP subflows limit to 0, creating an MPTCP endpoint with both the 'signal' and 'subflow' flags, creating a new MPTCP connection from a different address, and removing the MPTCP endpoint. The fix is available in kernel versions that have applied the patches. Linux kernel users should verify their kernel versions and apply the patches or update to a fixed version.

Defensive priority

Medium priority should be given to patching this vulnerability, as it can be triggered by a series of actions and has a MEDIUM severity score.

Recommended defensive actions

• Apply patches provided by the Linux kernel maintainers
• Update to a kernel version that includes the fix
• Monitor for potential exploitation attempts
• Implement compensating controls to mitigate the vulnerability
• Review and adjust MPTCP subflows limit and endpoint configurations
• Verify kernel versions and apply patches or updates
• Track exceptions and retest remediated assets

Evidence notes

The vulnerability was resolved by marking signal+subflow endpoints as used in the Linux kernel. The fix is available in kernel versions that have applied the patches. Linux kernel users should verify their kernel versions and apply the patches or update to a fixed version. Evidence is limited to public CVE details and supplied advisory text.

Sources and references

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.