All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Zhenpeng (Leo) Lin" <leo@depthfirst.com>
Cc: security@kernel.org, stable@vger.kernel.org,
	disclosures <disclosures@depthfirst.com>
Subject: Re: Exploitable reuseport cBPF UAF fixed in mainline but not backported to any stable/LTS
Date: Fri, 12 Jun 2026 09:38:15 +0200	[thread overview]
Message-ID: <2026061225-brisket-quickly-94b2@gregkh> (raw)
In-Reply-To: <CALPOzVk0gD2GnBjiPDQBfjsrf4b0hY3++KcOiaTV8gSFEifV6g@mail.gmail.com>

On Thu, Jun 11, 2026 at 03:01:15PM -0700, Zhenpeng (Leo) Lin wrote:
> Hello Linux kernel security team,

You also sent this to a public mailing list for some reason...

> Fix
> ---
> - Mainline commit 18fc650ccd7f ("bpf: Free reuseport cBPF prog after
>   RCU grace period.", Kuniyuki Iwashima), first released in v7.1-rc3.
>   It defers the cBPF free with call_rcu().

That commit has been queued up already for the next round of stable
kernel releases.

Next time, if you wish to have a commit applied to older kernels, please
take a look at:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

thanks,

greg k-h

      reply	other threads:[~2026-06-12  7:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11 22:01 Exploitable reuseport cBPF UAF fixed in mainline but not backported to any stable/LTS Zhenpeng (Leo) Lin
2026-06-12  7:38 ` Greg KH [this message]

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=2026061225-brisket-quickly-94b2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=disclosures@depthfirst.com \
    --cc=leo@depthfirst.com \
    --cc=security@kernel.org \
    --cc=stable@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.