All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Joakim Tjernlund (Nokia)" <joakim.tjernlund@nokia.com>
Cc: Sasha Levin <sashal@kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	"syzbot+937b5bbb6a815b3e5d0b@syzkaller.appspotmail.com"
	<syzbot+937b5bbb6a815b3e5d0b@syzkaller.appspotmail.com>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	"David S . Miller" <davem@davemloft.net>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	Neal Cardwell <ncardwell@google.com>,
	Matthieu Baerts <matttbe@kernel.org>,
	Mat Martineau <martineau@kernel.org>,
	Geliang Tang <geliang@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"mptcp@lists.linux.dev" <mptcp@lists.linux.dev>,
	"bcm-kernel-feedback-list@broadcom.com"
	<bcm-kernel-feedback-list@broadcom.com>,
	"Atul Joshi (Nokia)" <atul.joshi@nokia.com>
Subject: Re: [PATCH stable 6.12 v2] tcp: fix potential race in tcp_v6_syn_recv_sock()
Date: Mon, 7 Sep 2026 17:52:23 +0200	[thread overview]
Message-ID: <2026090706-dehydrate-hence-4fe8@gregkh> (raw)
In-Reply-To: <22b7bae35253cebe11b515d11b245d7c551c0f29.camel@nokia.com>

On Mon, Sep 07, 2026 at 03:34:45PM +0000, Joakim Tjernlund (Nokia) wrote:
> On Sun, 2026-09-06 at 09:33 -0400, Sasha Levin wrote:
> > 
> > 
> > > This fixes CVE-2026-43198 (v2 -- v1 broke the DCCP build by not updating
> > > every icsk_af_ops.syn_recv_sock implementer for the new argument).
> > 
> > Queued for 6.12, thanks.
> > 
> > --
> > Thanks,
> > Sasha
> 
> Hi
> 
> I do not see this one in the just released 6.12.109, maybe I am blind?

Nope, "next one".

thanks,

greg k-h

  reply	other threads:[~2026-09-07 15:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 18:34 [PATCH stable 5.10 v2] tcp: fix potential race in tcp_v6_syn_recv_sock() Florian Fainelli
2026-09-04 18:34 ` [PATCH stable 5.15 " Florian Fainelli
2026-09-06 13:33   ` Sasha Levin
2026-09-04 18:34 ` [PATCH stable 6.1 " Florian Fainelli
2026-09-05 18:35   ` sashiko-bot
2026-09-06 13:33   ` Sasha Levin
2026-09-04 18:34 ` [PATCH stable 6.12 " Florian Fainelli
2026-09-05 18:35   ` sashiko-bot
2026-09-06 13:33   ` Sasha Levin
2026-09-07 15:34     ` Joakim Tjernlund (Nokia)
2026-09-07 15:52       ` Greg KH [this message]
2026-09-04 18:35 ` [PATCH stable 6.6 " Florian Fainelli
2026-09-05 18:35   ` sashiko-bot
2026-09-06 13:33   ` Sasha Levin
2026-09-05 18:35 ` [PATCH stable 5.10 " sashiko-bot
2026-09-06 13:33 ` Sasha Levin

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=2026090706-dehydrate-hence-4fe8@gregkh \
    --to=greg@kroah.com \
    --cc=atul.joshi@nokia.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=geliang@kernel.org \
    --cc=horms@kernel.org \
    --cc=joakim.tjernlund@nokia.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+937b5bbb6a815b3e5d0b@syzkaller.appspotmail.com \
    /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.