From: Philip Li <philip.li@intel.com>
To: Dan Carpenter <error27@gmail.com>
Cc: Zihan Xi <zihanx@nebusec.ai>, <pc@manguebit.org>,
<linkinjeon@kernel.org>, <ronniesahlberg@gmail.com>,
<sprasad@microsoft.com>, <tom@talpey.com>,
<bharathsm@microsoft.com>, <dhowells@redhat.com>,
<stfrench@microsoft.com>, <linux-cifs@vger.kernel.org>,
<samba-technical@lists.samba.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>, kernel test robot <lkp@intel.com>,
Luxing Yin <root@tr0jan.top>
Subject: Re: [PATCH] smb: client: avoid NULL resp_iov dereference
Date: Mon, 28 Sep 2026 13:42:40 +0800 [thread overview]
Message-ID: <arn+UIhVhM4QDP0c@rli9-mobl> (raw)
In-Reply-To: <arkuJtmhKDAFnzTl@stanley.mountain>
On Sun, Sep 27, 2026 at 05:54:30PM +0300, Dan Carpenter wrote:
> On Sat, Sep 26, 2026 at 01:22:08PM +0000, Zihan Xi wrote:
> > compound_send_recv() only populates response vectors when resp_iov is
> > non-NULL. The final pre-authentication hash update nevertheless
> > dereferences resp_iov[0] whenever all compound requests complete.
> >
> > Guard the update with resp_iov to match the response-buffer handling and
> > avoid a NULL pointer dereference on callers that do not request response
> > vectors.
> >
> > Fixes: 62432a3f5145 ("cifs: Clean up some places where an extra kvec[] was required for rfc1002")
> > Cc: stable@vger.kernel.org
> > Reported-by: kernel test robot <lkp@intel.com>
> > Reported-by: Dan Carpenter <error27@gmail.com>
> > Closes: https://lore.kernel.org/all/202609241449.HlHmnZFZ-lkp@intel.com/
>
> Originally the idea was that I would review these and filter out
> the false positives, but these days people use lei to read email so
> they recieve the unfiltered warnings. The zero day bot should
> probably put a "Unfiltered warning" note at the top to let people
> know the warning hasn't been reviewed.
Got it, I will add this note to the bot report for unfiltered warnings.
Thanks
>
> regards,
> dan carpenter
>
>
>
next prev parent reply other threads:[~2026-09-28 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 13:22 Zihan Xi
2026-09-27 2:23 ` Namjae Jeon
2026-09-27 4:22 ` zihan xi
2026-09-27 14:54 ` Dan Carpenter
2026-09-28 5:42 ` Philip Li [this message]
2026-09-28 6:57 ` Dan Carpenter
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=arn+UIhVhM4QDP0c@rli9-mobl \
--to=philip.li@intel.com \
--cc=bharathsm@microsoft.com \
--cc=dhowells@redhat.com \
--cc=error27@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=root@tr0jan.top \
--cc=samba-technical@lists.samba.org \
--cc=sprasad@microsoft.com \
--cc=stable@vger.kernel.org \
--cc=stfrench@microsoft.com \
--cc=tom@talpey.com \
--cc=zihanx@nebusec.ai \
/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
all inboxes | Powered by JetHome®