Bug 2554819 (CVE-2026-98438) - CVE-2026-98438 kernel: mptcp: options: fix uninit-value in mptcp_write_data_fin
Summary: CVE-2026-98438 kernel: mptcp: options: fix uninit-value in mptcp_write_data_fin
Keywords:
Status: NEW
Alias: CVE-2026-98438
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-18 14:51 UTC by OSIDB Bzimport
Modified: 2026-10-19 10:33 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-18 14:51:21 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.