mptcp: options: fix uninit-value in mptcp_write_data_fin
- 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 7.2.7
- 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
Summary
In the Linux kernel, the following vulnerability has been resolved: mptcp: options: fix uninit-value in mptcp_write_data_fin When sending a DATA_FIN without data, and because the DATA_FIN occupies 1 octet of the connection-level sequence space [1], it is then required to add a DSS mapping with specific values. If the checksum has been negotiated, it also needs to be computed, and included in the outgoing packet, and thus the initial csum data needs to be reset to 0 as well. This is no longer the case since commit cfcceb7a39fc ("tcp: shrink per-packet memset in __tcp_transmit_skb()"), because the whole ext_copy structure is no longer zeroed by default. This seems to be the only case where use_map is changed and set afterwards, so initialising the csum field only in this case, along with other fields for this specific case.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From cfcceb7a39fc10a6f896af8229bf81d96acb22cc · fixed in 9a682067dd7b9dce6b94a0a05661dcc921446402; From cfcceb7a39fc10a6f896af8229bf81d96acb22cc · fixed in b110f1dd6cb6a9930503354a01a315e0a821eaa7
- Linux Linux
7.1
- KernelLinux
From 7.1.0 · fixed in 7.2.7