Linux CAN drivers development
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Eulgyu Kim <eulgyukim@snu.ac.kr>
Cc: mkl@pengutronix.de, linux-can@vger.kernel.org,
	linux-kernel@vger.kernel.org, byoungyoung@snu.ac.kr,
	jjy600901@snu.ac.kr, Vincent Mailhol <mailhol@kernel.org>
Subject: Re: [BUG] KASAN: slab-use-after-free Read in raw_rcv
Date: Mon, 4 May 2026 10:08:22 +0200	[thread overview]
Message-ID: <bc3edf17-3759-4bfd-bcca-bb9609fa1acb@hartkopp.net> (raw)
In-Reply-To: <20260504040839.20805-1-eulgyukim@snu.ac.kr>



On 04.05.26 06:08, Eulgyu Kim wrote:
>>>
>>> Can you confirm that the below patch fixes the issue?
>>>


> 
> Hello,
> 
> thanks for your reply.
> 
> We have tested the patch, and our reproducer did not trigger any issue.
> 
> As this issue was identified via fuzzing and we have limited background,
> we find it challenging to provide further verification.
> 
> At least for our specific test case, the issue seems to be resolved.
> 
> We hope this testing feedback is helpful.

Yes, it definitely is. Many thanks!

We will discuss the best way to add the suggested locking to the code 
here on the linux-can mailing list and then send a patch having you in 
the Reported-by tag.

Best regards,
Oliver

      reply	other threads:[~2026-05-04  8:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03 11:22 [BUG] KASAN: slab-use-after-free Read in raw_rcv Eulgyu Kim
2026-05-03 18:04 ` Oliver Hartkopp
2026-05-03 18:24   ` Oliver Hartkopp
2026-05-04  4:08   ` Eulgyu Kim
2026-05-04  8:08     ` Oliver Hartkopp [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=bc3edf17-3759-4bfd-bcca-bb9609fa1acb@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=byoungyoung@snu.ac.kr \
    --cc=eulgyukim@snu.ac.kr \
    --cc=jjy600901@snu.ac.kr \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailhol@kernel.org \
    --cc=mkl@pengutronix.de \
    /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