{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-45889", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-05-13T15:03:33.082Z", "datePublished": "2026-05-27T12:17:00.509Z", "dateUpdated": "2026-05-27T12:17:00.509Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-05-27T12:17:00.509Z"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: do not account for OoO in mptcp_rcvbuf_grow()\n\nMPTCP-level OoOs are physiological when multiple subflows are active\nconcurrently and will not cause retransmissions nor are caused by\ndrops.\n\nAccounting for them in mptcp_rcvbuf_grow() causes the rcvbuf slowly\ndrifting towards tcp_rmem[2].\n\nRemove such accounting. Note that subflows will still account for TCP-level\nOoO when the MPTCP-level rcvbuf is propagated.\n\nThis also closes a subtle and very unlikely race condition with rcvspace\ninit; active sockets with user-space holding the msk-level socket lock,\ncould complete such initialization in the receive callback, after that the\nfirst OoO data reaches the rcvbuf and potentially triggering a divide by\nzero Oops."}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["net/mptcp/protocol.c"], "versions": [{"version": "e118cdc34dd109562b64f6a397f68cd33b041d5b", "lessThan": "fb7bf00b04a6b48859f52035d4e745848c2b4c79", "status": "affected", "versionType": "git"}, {"version": "e118cdc34dd109562b64f6a397f68cd33b041d5b", "lessThan": "400ee4854adef1e4983812a3decf6717ea020136", "status": "affected", "versionType": "git"}, {"version": "e118cdc34dd109562b64f6a397f68cd33b041d5b", "lessThan": "6b329393502e5857662b851a13f947209c588587", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["net/mptcp/protocol.c"], "versions": [{"version": "6.18", "status": "affected"}, {"version": "0", "lessThan": "6.18", "status": "unaffected", "versionType": "semver"}, {"version": "6.18.14", "lessThanOrEqual": "6.18.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.19.4", "lessThanOrEqual": "6.19.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.0", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.18", "versionEndExcluding": "6.18.14"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.18", "versionEndExcluding": "6.19.4"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.18", "versionEndExcluding": "7.0"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/fb7bf00b04a6b48859f52035d4e745848c2b4c79"}, {"url": "https://git.kernel.org/stable/c/400ee4854adef1e4983812a3decf6717ea020136"}, {"url": "https://git.kernel.org/stable/c/6b329393502e5857662b851a13f947209c588587"}], "title": "mptcp: do not account for OoO in mptcp_rcvbuf_grow()", "x_generator": {"engine": "bippy-1.2.0"}}}}

{}

{"cveTags": [], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: do not account for OoO in mptcp_rcvbuf_grow()\n\nMPTCP-level OoOs are physiological when multiple subflows are active\nconcurrently and will not cause retransmissions nor are caused by\ndrops.\n\nAccounting for them in mptcp_rcvbuf_grow() causes the rcvbuf slowly\ndrifting towards tcp_rmem[2].\n\nRemove such accounting. Note that subflows will still account for TCP-level\nOoO when the MPTCP-level rcvbuf is propagated.\n\nThis also closes a subtle and very unlikely race condition with rcvspace\ninit; active sockets with user-space holding the msk-level socket lock,\ncould complete such initialization in the receive callback, after that the\nfirst OoO data reaches the rcvbuf and potentially triggering a divide by\nzero Oops."}], "id": "CVE-2026-45889", "lastModified": "2026-05-27T14:48:31.480", "metrics": {}, "published": "2026-05-27T14:17:02.927", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/400ee4854adef1e4983812a3decf6717ea020136"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/6b329393502e5857662b851a13f947209c588587"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/fb7bf00b04a6b48859f52035d4e745848c2b4c79"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Awaiting Analysis"}

{}

{}