mptcp: cope racing subflow creation in mptcp_rcv_space_adjust
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.174, 6.1.119, 6.6.63, 6.11.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: mptcp: cope racing subflow creation in mptcp_rcv_space_adjust Additional active subflows - i.e. created by the in kernel path manager - are included into the subflow list before starting the 3whs. A racing recvmsg() spooling data received on an already established subflow would unconditionally call tcp_cleanup_rbuf() on all the current subflows, potentially hitting a divide by zero error on the newly created ones. Explicitly check that the subflow is in a suitable state before invoking tcp_cleanup_rbuf().
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From c76c6956566f974bac2470bd72fc22fb923e04a1 · fixed in 0a9a182ea5c7bb0374e527130fd85024ace7279b; From c76c6956566f974bac2470bd72fc22fb923e04a1 · fixed in 24995851d58c4a205ad0ffa7b2f21e479a9c8527; From c76c6956566f974bac2470bd72fc22fb923e04a1 · fixed in ff825ab2f455299c0c7287550915a8878e2a66e0; From c76c6956566f974bac2470bd72fc22fb923e04a1 · fixed in aad6412c63baa39dd813e81f16a14d976b3de2e8; From c76c6956566f974bac2470bd72fc22fb923e04a1 · fixed in ce7356ae35943cc6494cc692e62d51a734062b7d
- Linux Linux
5.10
- KernelLinux
From 5.10.0 · fixed in 5.15.174; From 5.16.0 · fixed in 6.1.119; From 6.2.0 · fixed in 6.6.63; From 6.7.0 · fixed in 6.11.10