CVE-2026-64422
Last modified
CVE-2026-64422 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 2.6.24.1, < 5.10.261 |
| Linux | Linux Kernel | >= 5.11, < 5.15.212 |
| Linux | Linux Kernel | >= 5.16, < 6.1.178 |
| Linux | Linux Kernel | >= 6.2, < 6.6.145 |
| Linux | Linux Kernel | >= 6.7, < 6.12.96 |
| Linux | Linux Kernel | >= 6.13, < 6.18.39 |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 |
| Linux | Linux Kernel | 2.6.24 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-64422?
How severe is CVE-2026-64422?
How do I fix CVE-2026-64422?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64417In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64418In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64419In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-6442Improper validation of bash commands in Snowflake Cortex Cod…8.3
- CVE-2026-64420In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-64421In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64423In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64424In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64425In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64426In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64427In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64428In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-64422?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
