CVE-2026-64422
net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes
Description
In the Linux kernel, the following vulnerability has been resolved: net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes Reject invalid `net.ipv4.tcp_reordering` values before they reach TCP socket state. The sysctl is stored as an `int` but copied into the `u32` `tp->reordering` field for new sockets, so negative writes wrap to large values. With `tcp_mtu_probing=2`, the wrapped value can overflow the `tcp_mtu_probe()` size calculation and drive the MTU probing path into an out-of-bounds read. Route `tcp_reordering` writes through `proc_dointvec_minmax()` and require it to be at least 1. Also require `tcp_max_reordering` to be at least 1 so the configured maximum cannot become negative either. When registering the table for a non-init network namespace, relocate `extra2` pointers that refer into `init_net.ipv4` so the `tcp_reordering` upper bound follows that namespace's `tcp_max_reordering`. Harden `tcp_mtu_probe()` itself by computing `size_needed` as `u64`. This keeps the send queue and window checks from being bypassed through signed integer overflow.
INFO
Published Date :
July 25, 2026, 10:17 a.m.
Last Modified :
July 25, 2026, 10:17 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64422
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the Linux kernel to a patched version.
- Ensure tcp_reordering and tcp_max_reordering are at least 1.
- Harden tcp_mtu_probe with u64 for size calculations.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64422.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64422 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64422
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64422 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64422 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 25, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '91cc17c0e5e5ada156a8d5787a2509d263ea6bbf', 'lessThan': 'f0d88a4cd03affff6c08adf6c63964e235aede43', 'versionType': 'git'}, {'status': 'affected', 'version': '91cc17c0e5e5ada156a8d5787a2509d263ea6bbf', 'lessThan': '27ddf4486c7dbf5bdd393fa8bef6b67179796d98', 'versionType': 'git'}, {'status': 'affected', 'version': '91cc17c0e5e5ada156a8d5787a2509d263ea6bbf', 'lessThan': '782708ca1ea1f68b8cbb5ea3a7f5f18d0000efae', 'versionType': 'git'}, {'status': 'affected', 'version': '91cc17c0e5e5ada156a8d5787a2509d263ea6bbf', 'lessThan': 'e81f805824a8109504fce090641b17d135b48cd1', 'versionType': 'git'}, {'status': 'affected', 'version': '91cc17c0e5e5ada156a8d5787a2509d263ea6bbf', 'lessThan': '99206ce2244f8a3ed64298d0667c9055845a5dc7', 'versionType': 'git'}, {'status': 'affected', 'version': '91cc17c0e5e5ada156a8d5787a2509d263ea6bbf', 'lessThan': 'bbae351c0f32f7c200249e4aa6561b2b419dcf69', 'versionType': 'git'}, {'status': 'affected', 'version': '91cc17c0e5e5ada156a8d5787a2509d263ea6bbf', 'lessThan': 'a094ac95d3b69adfa1676eb9c8eae6835d4f1671', 'versionType': 'git'}, {'status': 'affected', 'version': '91cc17c0e5e5ada156a8d5787a2509d263ea6bbf', 'lessThan': 'efb8763d7bbb40cff4cc55a6b62c3095a038149c', 'versionType': 'git'}], 'programFiles': ['net/ipv4/sysctl_net_ipv4.c', 'net/ipv4/tcp_output.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '2.6.24'}, {'status': 'unaffected', 'version': '0', 'lessThan': '2.6.24', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.261', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.212', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.178', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.145', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.96', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.39', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.4', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['net/ipv4/sysctl_net_ipv4.c', 'net/ipv4/tcp_output.c'], 'defaultStatus': 'affected'}] Added Description In the Linux kernel, the following vulnerability has been resolved: net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes Reject invalid `net.ipv4.tcp_reordering` values before they reach TCP socket state. The sysctl is stored as an `int` but copied into the `u32` `tp->reordering` field for new sockets, so negative writes wrap to large values. With `tcp_mtu_probing=2`, the wrapped value can overflow the `tcp_mtu_probe()` size calculation and drive the MTU probing path into an out-of-bounds read. Route `tcp_reordering` writes through `proc_dointvec_minmax()` and require it to be at least 1. Also require `tcp_max_reordering` to be at least 1 so the configured maximum cannot become negative either. When registering the table for a non-init network namespace, relocate `extra2` pointers that refer into `init_net.ipv4` so the `tcp_reordering` upper bound follows that namespace's `tcp_max_reordering`. Harden `tcp_mtu_probe()` itself by computing `size_needed` as `u64`. This keeps the send queue and window checks from being bypassed through signed integer overflow. Added Reference https://git.kernel.org/stable/c/27ddf4486c7dbf5bdd393fa8bef6b67179796d98 Added Reference https://git.kernel.org/stable/c/782708ca1ea1f68b8cbb5ea3a7f5f18d0000efae Added Reference https://git.kernel.org/stable/c/99206ce2244f8a3ed64298d0667c9055845a5dc7 Added Reference https://git.kernel.org/stable/c/a094ac95d3b69adfa1676eb9c8eae6835d4f1671 Added Reference https://git.kernel.org/stable/c/bbae351c0f32f7c200249e4aa6561b2b419dcf69 Added Reference https://git.kernel.org/stable/c/e81f805824a8109504fce090641b17d135b48cd1 Added Reference https://git.kernel.org/stable/c/efb8763d7bbb40cff4cc55a6b62c3095a038149c Added Reference https://git.kernel.org/stable/c/f0d88a4cd03affff6c08adf6c63964e235aede43