[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024120252-CVE-2024-53122-f35c@gregkh>
Date: Mon, 2 Dec 2024 14:53:01 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-53122: mptcp: cope racing subflow creation in mptcp_rcv_space_adjust
Description
===========
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().
The Linux kernel CVE team has assigned CVE-2024-53122 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10 with commit c76c6956566f and fixed in 6.1.119 with commit 24995851d58c
Issue introduced in 5.10 with commit c76c6956566f and fixed in 6.6.63 with commit ff825ab2f455
Issue introduced in 5.10 with commit c76c6956566f and fixed in 6.11.10 with commit aad6412c63ba
Issue introduced in 5.10 with commit c76c6956566f and fixed in 6.12 with commit ce7356ae3594
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2024-53122
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
net/mptcp/protocol.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/24995851d58c4a205ad0ffa7b2f21e479a9c8527
https://git.kernel.org/stable/c/ff825ab2f455299c0c7287550915a8878e2a66e0
https://git.kernel.org/stable/c/aad6412c63baa39dd813e81f16a14d976b3de2e8
https://git.kernel.org/stable/c/ce7356ae35943cc6494cc692e62d51a734062b7d
Powered by blists - more mailing lists