netdev - Re: [PATCH stable] xdp: Reset bpf_redirect_info before running a xdp's BPF prog.

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250317140849.H4eSnqFl@linutronix.de>
Date: Mon, 17 Mar 2025 15:08:49 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: stable@...r.kernel.org, netdev@...r.kernel.org, bpf@...r.kernel.org,
	Ricardo Cañuelo Navarro <rcn@...lia.com>,
	Alexei Starovoitov <ast@...nel.org>,
	Andrii Nakryiko <andrii@...nel.org>,
	Daniel Borkmann <daniel@...earbox.net>,
	"David S. Miller" <davem@...emloft.net>,
	Jakub Kicinski <kuba@...nel.org>,
	Jesper Dangaard Brouer <hawk@...nel.org>,
	John Fastabend <john.fastabend@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Toke Høiland-Jørgensen <toke@...nel.org>
Subject: Re: [PATCH stable] xdp: Reset bpf_redirect_info before running a
 xdp's BPF prog.

> > I added the commit introducing map redirects as the origin of the
> > problem which is v4.14-rc1. The code is a bit different there it seems
> > to work similar.
> 
> What stable tree(s) is this for?  Just 6.6.y?  Why not older ones?

I didn't say just v6.6.y. The commit introducing the problem is in
v4.14-rc1 so I would say all the way down for the supported trees. Just
let me know if it does not apply for some of the older kernel.

> > Greg, feel free to decide if this is worth a CVE.
> 
> That's not how CVEs are assigned :)
> 
> If you want one, please read the in-tree documentation we have for that.

I don't need one but it is tempting to go through the new process :).
If it does not make your handling here easier (since you have two
different patches for one issue) there is no need for it from my side.

Thank you.

> thanks,
> 
> greg k-h

Sebastian