netdev - Re: [PATCH bpf-next 2/5] net/smc: fix UAF on smcsk after smc_listen

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250818053936.GA28521@j66a10360.sqa.eu95>
Date: Mon, 18 Aug 2025 13:39:36 +0800
From: "D. Wythe" <alibuda@...ux.alibaba.com    >
To: Jakub Kicinski <kuba@...nel.org>
Cc: Alexandra Winter <wintera@...ux.ibm.com>,
	"D. Wythe" <alibuda@...ux.alibaba.com>, ast@...nel.org,
	daniel@...earbox.net, andrii@...nel.org, martin.lau@...ux.dev,
	pabeni@...hat.com, song@...nel.org, sdf@...gle.com,
	haoluo@...gle.com, yhs@...com, edumazet@...gle.com,
	john.fastabend@...il.com, kpsingh@...nel.org, jolsa@...nel.org,
	Mahanta.Jambigi@....com, Sidraya.Jayagond@....com,
	wenjia@...ux.ibm.com, dust.li@...ux.alibaba.com,
	tonylu@...ux.alibaba.com, guwen@...ux.alibaba.com,
	bpf@...r.kernel.org, davem@...emloft.net, netdev@...r.kernel.org,
	jaka@...ux.ibm.com
Subject: Re: [PATCH bpf-next 2/5] net/smc: fix UAF on smcsk after
 smc_listen_out()

On Mon, Aug 11, 2025 at 08:33:56AM -0700, Jakub Kicinski wrote:
> On Mon, 11 Aug 2025 11:24:50 +0200 Alexandra Winter wrote:
> > > Yes, it should be sent to net. But the problem is that if I don't carry
> > > this patch, the BPF CI test will always crash. Maybe I should send a
> > > copy to both net and bpf-next? Do you have any suggestions?
> > 
> > I do not have any experience with bpf-next. But typically patches
> > to 'net' are taken after one or two days, if there are no issues.
> > I'd assume they are then picked to net-next and bpf-next(?) almost instantly.
> > Then you would not need it in your bpf series anymore.
> 
> AFAIU the patches which land in net will make it to -next trees after
> respective PR with fixes. So
> 
> 
>  patch -> 
>           net ->
>                  [next Thu] Linus ->
>                                       [same day] net-next
>                                       [at some point] bpf PR ->
>                                                                  Linux
>                                                                         -> bpf-next
> 
> What gets applied to net should be in net-next in a week,
> and most -next trees within 2 weeks.

That's very helpful.

Based on those infomations, I will send this prerequisite patch to the net
tree first. I'll then wait for about two weeks for it to propagate to
bpf-next before submitting the rest of my BPF series.

Best regards,
D. Wythe