From: Michal Hocko <mhocko@suse.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
Eric Dumazet <edumazet@google.com>,
linux-cve-announce@vger.kernel.org
Subject: Re: CVE-2024-35840: mptcp: use OPTION_MPTCP_MPJ_SYNACK in subflow_finish_connect()
Date: Mon, 17 Jun 2024 13:41:22 +0200 [thread overview]
Message-ID: <ZnAg4ndsrYCuqN6j@tiehlicka> (raw)
In-Reply-To: <2024061743-aversion-uncured-d770@gregkh>
On Mon 17-06-24 13:31:13, Greg KH wrote:
> On Mon, Jun 17, 2024 at 01:28:05PM +0200, Michal Hocko wrote:
> > On Thu 06-06-24 10:03:59, Michal Hocko wrote:
> > > Hi,
> > > what is the actual security threat here? As far as I can see, the
> > > problem that the commit requested here addresses seems to be rather
> > > functional, rather than responding to an unexpected packet options with
> > > a reset, we actually establish a connection with some garbage parameters
> > > (likely unpredictable). Which is unfortunate but I do not see any
> > > security implications.
> >
> > Does the silence mean that there are no actual security implications
> > here?
>
> Sorry, no, I was traveling and am still trying to catch up with the
> pending queue. Should get to it later today or tomorrow, sorry for the
> delay.
Thanks!
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2024-06-17 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 14:27 CVE-2024-35840: mptcp: use OPTION_MPTCP_MPJ_SYNACK in subflow_finish_connect() Greg Kroah-Hartman
2024-06-06 8:03 ` Michal Hocko
2024-06-17 11:28 ` Michal Hocko
2024-06-17 11:31 ` Greg Kroah-Hartman
2024-06-17 11:41 ` Michal Hocko [this message]
2024-06-17 15:43 ` Greg Kroah-Hartman
2024-06-17 15:59 ` Michal Hocko
2024-06-17 17:47 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZnAg4ndsrYCuqN6j@tiehlicka \
--to=mhocko@suse.com \
--cc=cve@kernel.org \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.