The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jaeyoung Chung <jjy600901@snu.ac.kr>
Cc: jirislaby@kernel.org, linux-serial@vger.kernel.org,
	linux-kernel@vger.kernel.org, eulgyukim@snu.ac.kr
Subject: Re: [BUG] KASAN: slab-use-after-free Read in __timer_delete
Date: Mon, 24 Aug 2026 17:12:11 +0200	[thread overview]
Message-ID: <2026082445-peddling-brigade-34ab@gregkh> (raw)
In-Reply-To: <20260824145314.2148275-1-jjy600901@snu.ac.kr>

On Mon, Aug 24, 2026 at 11:53:13PM +0900, Jaeyoung Chung wrote:
> Hello,
> 
> We found a "KASAN: slab-use-after-free Read in __timer_delete" on Linux v7.2.
> The issue was found by our own race fuzzer. We have not analyzed the root cause,
> so we do not have a proposed fix to offer.
> 
> To reproduce the race reliably, we applied the delay patch below to the
> kernel and ran the C reproducer as root inside an x86_64 QEMU guest. The
> crash log we observed, the delay patch and the reproducer are all included
> below.
> 
> The following kernel config options are required to reproduce the issue:
>     CONFIG_N_GSM=y
>     CONFIG_TTY=y
>     CONFIG_KASAN=y
> 
> We hope this report is useful. Please let us know if any further
> information would help.

Please see the email archives for why attempting to fuzz this file is
not going to go well, and why you should just ignore it UNLESS you have
this hardware.

thanks,

greg k-h

      reply	other threads:[~2026-08-24 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 14:53 [BUG] KASAN: slab-use-after-free Read in __timer_delete Jaeyoung Chung
2026-08-24 15:12 ` Greg KH [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=2026082445-peddling-brigade-34ab@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=eulgyukim@snu.ac.kr \
    --cc=jirislaby@kernel.org \
    --cc=jjy600901@snu.ac.kr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    /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