CVE-2026-64422

net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes

HIGH
7.1
CVSS Score
Published: July 25, 2026 at 08:51 AM UTC
Updated: October 19, 2026 at 09:17 PM UTC
4 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSiplus S7-1500 CPU 1518-4 Pn /dp MFP Firmware

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.1
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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.

Affected

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

2.6.24.1 ≤ v < 5.10.2615.11 ≤ v < 5.15.2125.16 ≤ v < 6.1.1786.13 ≤ v < 6.18.396.19 ≤ v < 7.1.46.2 ≤ v < 6.6.1456.7 ≤ v < 6.12.962.6.242.6.24 rc42.6.24 rc52.6.24 rc62.6.24 rc72.6.24 rc891cc17c0e5e5ada156a8d5787a2509d263ea6bbf
Vendor states this is fixed in 27ddf4486c7dbf5bdd393fa8bef6b67179796d98 (fixed)
Vendor states this is fixed in 782708ca1ea1f68b8cbb5ea3a7f5f18d0000efae (fixed)
Vendor states this is fixed in 99206ce2244f8a3ed64298d0667c9055845a5dc7 (fixed)
Vendor states this is fixed in a094ac95d3b69adfa1676eb9c8eae6835d4f1671 (fixed)
Vendor states this is fixed in bbae351c0f32f7c200249e4aa6561b2b419dcf69 (fixed)
Vendor states this is fixed in e81f805824a8109504fce090641b17d135b48cd1 (fixed)
Vendor states this is fixed in efb8763d7bbb40cff4cc55a6b62c3095a038149c (fixed)
Vendor states this is fixed in f0d88a4cd03affff6c08adf6c63964e235aede43 (fixed)
Vendor states this is fixed in 2.6.24 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

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

CVSS

7.1HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-190

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