From: Greg KH <gregkh@linuxfoundation.org>
To: Cyber_black <Cyberblackk@proton.me>
Cc: "security@kernel.org" <security@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"david+nfc@ixit.cz" <david+nfc@ixit.cz>,
"oe-linux-nfc@lists.linux.dev" <oe-linux-nfc@lists.linux.dev>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>, "w@1wt.eu" <w@1wt.eu>
Subject: Re: NFC/LLCP: unsafe userspace sockaddr handling in bind/connect paths
Date: Sat, 30 May 2026 18:00:37 +0200 [thread overview]
Message-ID: <2026053008-level-debrief-7f65@gregkh> (raw)
In-Reply-To: <0AJFeQ-7iEFm2WdHkRhf_kX_3FFbc3ONYxT3fxz75i4eAP8glmc1jmY7JOHngN73P9L6yPrflvcZs63EHu_XazAsLhPIe0zUrtdK7cKnC6Q=@proton.me>
On Sat, May 30, 2026 at 12:15:37PM +0000, Cyber_black wrote:
> SUGGESTED FIX
<snip>
As documented, please just send a real patch for this so that it can be
applied properly.
thanks,
greg k-h
parent reply other threads:[~2026-05-30 16:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0AJFeQ-7iEFm2WdHkRhf_kX_3FFbc3ONYxT3fxz75i4eAP8glmc1jmY7JOHngN73P9L6yPrflvcZs63EHu_XazAsLhPIe0zUrtdK7cKnC6Q=@proton.me>]
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=2026053008-level-debrief-7f65@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Cyberblackk@proton.me \
--cc=davem@davemloft.net \
--cc=david+nfc@ixit.cz \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=security@kernel.org \
--cc=w@1wt.eu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox