All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jaeyeong Lee <iostreampy@proton.me>
Cc: "pablo@netfilter.org" <pablo@netfilter.org>,
	"fw@strlen.de" <fw@strlen.de>, "phil@nwl.cc" <phil@nwl.cc>,
	"netfilter-devel@vger.kernel.org"
	<netfilter-devel@vger.kernel.org>,
	"security@kernel.org" <security@kernel.org>
Subject: Re: netfilter: nf_nat_sip expectation UAF permits local privilege escalation
Date: Sat, 11 Jul 2026 07:29:39 +0200	[thread overview]
Message-ID: <2026071134-turkey-detonator-0d87@gregkh> (raw)
In-Reply-To: <aQrSf6maL27cH2V4V9ELFdSqdtCWQ-B5iZr8fjR2Wz7zAJ7L32oW50bdrePoTMnJ4CRjDrns-jNMNFHGWNUxYe3UcV91AK99Ilncjab2uDk=@proton.me>

On Fri, Jul 10, 2026 at 11:19:54PM +0000, Jaeyeong Lee wrote:
> ## Vulnerability Summary

<snip>

As you sent this to a public mailing list, there's no need for
security@kernel.org to be involved in it.

Also, please just submit a patch to resolve this issue so that it gets
fixed and you get full credit for resolving it.

thanks,

greg k-h

  reply	other threads:[~2026-07-11  5:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10 23:19 netfilter: nf_nat_sip expectation UAF permits local privilege escalation Jaeyeong Lee
2026-07-11  5:29 ` Greg KH [this message]
2026-07-11 14:21   ` [PATCH nf] netfilter: nf_nat: do not reuse an unexpected expectation on RTCP clash Jaeyeong Lee
2026-07-11 16:29     ` Florian Westphal
2026-07-12  5:54       ` Greg KH
2026-07-12  7:40         ` Florian Westphal
2026-07-12  7:54           ` Greg KH
2026-07-12  8:08             ` Florian Westphal
2026-07-12  8:20               ` Greg KH
2026-07-12  8:40                 ` panic_on_warn and lack of lesser-WARN (was: Re: [PATCH nf] netfilter: nf_nat: do not reuse an unexpected expectation on RTCP clash) Florian Westphal

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=2026071134-turkey-detonator-0d87@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=fw@strlen.de \
    --cc=iostreampy@proton.me \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=phil@nwl.cc \
    --cc=security@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.