CVE-2026-23247
Received Received - Intake
Off-Path TCP Source Port Leakage in Linux Kernel via SYN Cookie Side-Channel

Publication date: 2026-03-18

Last updated on: 2026-03-18

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: tcp: secure_seq: add back ports to TS offset This reverts 28ee1b746f49 ("secure_seq: downgrade to per-host timestamp offsets") tcp_tw_recycle went away in 2017. Zhouyan Deng reported off-path TCP source port leakage via SYN cookie side-channel that can be fixed in multiple ways. One of them is to bring back TCP ports in TS offset randomization. As a bonus, we perform a single siphash() computation to provide both an ISN and a TS offset.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-18
Last Modified
2026-03-18
Generated
2026-05-07
AI Q&A
2026-03-18
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability involves an off-path TCP source port leakage via a SYN cookie side-channel in the Linux kernel's TCP implementation.

The issue was related to the way TCP timestamp offsets were handled, specifically after the removal of tcp_tw_recycle in 2017.

To fix this, the Linux kernel reverted a previous change and added back ports to the TCP timestamp offset randomization, improving security by preventing the leakage.

Additionally, a single siphash() computation is now used to provide both an Initial Sequence Number (ISN) and a timestamp offset.


How can this vulnerability impact me? :

This vulnerability could allow an attacker to leak TCP source port information via a side-channel attack, potentially enabling off-path attackers to infer connection details.

Such leakage can be used to facilitate further attacks on TCP connections, such as spoofing or hijacking sessions, compromising network security.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart