CVE-2026-45889

published 27 May 2026 · updated 27 May 2026

mptcp: do not account for OoO in mptcp_rcvbuf_grow()

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 400ee4854adef1e4983812a3decf6717ea020136, Kernel 6b329393502e5857662b851a13f947209c588587 and Kernel fb7bf00b04a6b48859f52035d4e745848c2b4c79.

In the Linux kernel, the following vulnerability has been resolved: mptcp: do not account for OoO in mptcp_rcvbuf_grow() MPTCP-level OoOs are physiological when multiple subflows are active concurrently and will not cause retransmissions nor are caused by drops. Accounting for them in mptcp_rcvbuf_grow() causes the rcvbuf slowly drifting towards tcp_rmem[2]. Remove such accounting. Note that subflows will still account for TCP-level OoO when the MPTCP-level rcvbuf is propagated. This also closes a subtle and very unlikely race condition with rcvspace init; active sockets with user-space holding the msk-level socket lock, could complete such initialization in the receive callback, after that the first OoO data reaches the rcvbuf and potentially triggering a divide by zero Oops.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.18, >=e118cdc34dd109562b64f6a397f68cd33b041d5b <400ee4854adef1e4983812a3decf6717ea020136, >=e118cdc34dd109562b64f6a397f68cd33b041d5b <6b329393502e5857662b851a13f947209c588587, >=e118cdc34dd109562b64f6a397f68cd33b041d5b <fb7bf00b04a6b48859f52035d4e745848c2b4c79400ee4854adef1e4983812a3decf6717ea020136, 6b329393502e5857662b851a13f947209c588587, fb7bf00b04a6b48859f52035d4e745848c2b4c79

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-45889 severity on Zeptric[![CVE-2026-45889](https://zeptric.io/badge/cve/CVE-2026-45889.svg)](https://zeptric.io/cve/CVE-2026-45889)