From: Enzo Matsumiya <ematsumiya@suse.de>
To: kernel test robot <oliver.sang@intel.com>
Cc: lkp@lists.01.org, lkp@intel.com, linux-cifs@vger.kernel.org,
samba-technical@lists.samba.org, smfrench@gmail.com, pc@cjr.nz,
ronniesahlberg@gmail.com, nspmangalore@gmail.com
Subject: Re: [cifs] c9ba95b978: BUG:KASAN:use-after-free_in_SMB2_sess_free_buffer[cifs]
Date: Tue, 20 Sep 2022 11:43:22 -0300 [thread overview]
Message-ID: <20220920144322.tkd6eeezfeesva3r@suse.de> (raw)
In-Reply-To: <202209201529.ec633796-oliver.sang@intel.com>
On 09/20, kernel test robot wrote:
>
>Greeting,
>
>FYI, we noticed the following commit (built with gcc-11):
>
>commit: c9ba95b978808970633b0221b70c5255ebc8630e ("[PATCH v2] cifs: replace kfree() with kfree_sensitive() for sensitive data")
>url: https://github.com/intel-lab-lkp/linux/commits/Enzo-Matsumiya/cifs-replace-kfree-with-kfree_sensitive-for-sensitive-data/20220918-113758
>base: git://git.samba.org/sfrench/cifs-2.6.git for-next
>patch link: https://lore.kernel.org/linux-cifs/20220918033619.16522-1-ematsumiya@suse.de
>
snip
>If you fix the issue, kindly add following tag
>| Reported-by: kernel test robot <oliver.sang@intel.com>
>| Link: https://lore.kernel.org/r/202209201529.ec633796-oliver.sang@intel.com
snip
>kern :info : [ 81.927031] CIFS: Attempting to mount \\localhost\fs
>kern :err : [ 81.949059] ==================================================================
>kern :err : [ 81.956956] BUG: KASAN: use-after-free in SMB2_sess_free_buffer+0xba/0x1c0 [cifs]
>kern :err : [ 81.965177] Write of size 44 at addr ffff8881219a3c00 by task mount.cifs/1530
Will send v2.
Enzo
prev parent reply other threads:[~2022-09-20 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 3:36 [PATCH v2] cifs: replace kfree() with kfree_sensitive() for sensitive data Enzo Matsumiya
[not found] ` <202209201529.ec633796-oliver.sang@intel.com>
2022-09-20 14:43 ` Enzo Matsumiya [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=20220920144322.tkd6eeezfeesva3r@suse.de \
--to=ematsumiya@suse.de \
--cc=linux-cifs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=nspmangalore@gmail.com \
--cc=oliver.sang@intel.com \
--cc=pc@cjr.nz \
--cc=ronniesahlberg@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).