Skip to main content
VulnerabilityPublished Updated

CVE-2026-53183: Linux kernel · mptcp: allow subflow rcv wnd to shrink

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High · fixed in da23be77e1292cd611e736c3aa17da633d7ddce7 : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in da23be77e1292cd611e736c3aa17da633d7ddce7, c297a4e65c50a2b807d9309b22615080faffa8f3, bf364b0f10b27679140699821f88af7f01e2a6e3 +3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ f3589be0c420a3137e5902d15705ced6a36f3f43, < da23be77e1292cd611e736c3aa17da633d7ddce7
Fixed in
  • da23be77e1292cd611e736c3aa17da633d7ddce7
LinuxLinuxAffected
  • ≥ f3589be0c420a3137e5902d15705ced6a36f3f43, < c297a4e65c50a2b807d9309b22615080faffa8f3
Fixed in
  • c297a4e65c50a2b807d9309b22615080faffa8f3
LinuxLinuxAffected
  • ≥ f3589be0c420a3137e5902d15705ced6a36f3f43, < bf364b0f10b27679140699821f88af7f01e2a6e3
Fixed in
  • bf364b0f10b27679140699821f88af7f01e2a6e3
LinuxLinuxAffected
  • ≥ f3589be0c420a3137e5902d15705ced6a36f3f43, < b1fd13074f22105deec45aa02283e322733e0c2d
Fixed in
  • b1fd13074f22105deec45aa02283e322733e0c2d
LinuxLinuxAffected
  • ≥ f3589be0c420a3137e5902d15705ced6a36f3f43, < aa3861f40ac32706d9e97bfac76984613e278788
Fixed in
  • aa3861f40ac32706d9e97bfac76984613e278788
LinuxLinuxAffected
  • ≥ f3589be0c420a3137e5902d15705ced6a36f3f43, < 653245266913f03fcf21cbca68eed5c197a33e52
Fixed in
  • 653245266913f03fcf21cbca68eed5c197a33e52

Description

In the Linux kernel, the following vulnerability has been resolved: mptcp: allow subflow rcv wnd to shrink In MPTCP connection, the `window` field in the TCP header refers to the MPTCP-level rcv_nxt and it's right edge should not move backward. Such constraint is enforced at DSS option generation time. At the same time, the TCP stack ensures independently that the TCP-level rcv wnd right's edge does not move backward. That in turn causes artificial inflating of the MPTCP rcv window when the incoming data is acked at the TCP level and is OoO in the MPTCP sequence space (or lands in the backlog). As a consequence, the incoming traffic can exceed the receiver rcvbuf size even when the sender is not misbehaving. Prevent such scenario forcibly allowing the TCP subflow to shrink the TCP-level rcv wnd regardless of the current netns setting.

References

Community reviews

Loading reviews…