All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Abagail ren <renzezhongucas@gmail.com>,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller@googlegroups.com
Subject: Re: KASAN: slab-use-after-free Read in nfc_llcp_unregister_device
Date: Wed, 25 Oct 2023 09:23:18 +0200	[thread overview]
Message-ID: <32edfc3c-321e-4816-b634-7b9540ab8c47@linaro.org> (raw)
In-Reply-To: <CALkECRjyG8AtbUunWFYErQethdyCfiNC2-ZHP6oVtO3+GHxahA@mail.gmail.com>

On 25/10/2023 08:27, Abagail ren wrote:
> Good day, dear maintainers.
> 
> Since the email system replied that it refused to accept the email because
> the text contained HTML, I sent it to you again in the form of shared files.
> 
> We found a bug using a modified kernel configuration file used by syzbot.
> 
> We enhanced the probability of vulnerability discovery using our prototype
> system developed based on syzkaller and found a bug "' KASAN:
> slab-use-after-free Read in nfc_llcp_unregister_device." I'm still working
> on it to find out its root cause and availability.
> 
> The stack information:
> https://docs.google.com/document/d/1gdHebCRsvVsSPKfilcoXVu3Pctvoj2FSZCACcVYZXns/edit?usp=sharing
> 
> Kernel Branch: 6.4.0-rc3
> 

Hi,

I received two emails from you, so I am not sure if these are separate
issues or not.

Anyway, there were fixes to these paths and you are testing quite old
kernel. If you have the reproducer, it should be straightforward to test
new kernel, so please do so. Test on linux-next.

> Kernel Config:
> https://docs.google.com/document/d/1WIM0btqS2dex18HQYaL2xyoW6WdX2TsaNguTnWzHMps/edit?usp=sharing
> 
> Reproducer:
> https://docs.google.com/document/d/1LrgGdOgZwO8wz0opusZ7flP9QSFZa32GdozvoxGysyY/edit?usp=sharing


Best regards,
Krzysztof


  parent reply	other threads:[~2023-10-25  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALkECRjyG8AtbUunWFYErQethdyCfiNC2-ZHP6oVtO3+GHxahA@mail.gmail.com>
2023-10-25  7:12 ` KASAN: slab-use-after-free Read in nfc_llcp_unregister_device Aleksandr Nogikh
2023-10-25  7:23 ` Krzysztof Kozlowski [this message]
2023-10-25  4:14 Abagail ren

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=32edfc3c-321e-4816-b634-7b9540ab8c47@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=renzezhongucas@gmail.com \
    --cc=syzkaller@googlegroups.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 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.