From: sashiko-bot@kernel.org
To: "Hui Peng" <benquike@gmail.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH v5 1/3] serial: 8250: hold hash_mutex across IRQ chain linking in serial_link_irq_chain()
Date: Wed, 30 Sep 2026 04:19:31 +0000 [thread overview]
Message-ID: <20260930041931.C4AC61F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260930041216.155911-2-benquike@gmail.com>
> In serial_link_irq_chain(), serial_get_or_create_irq_info() acquires
> hash_mutex to search or allocate a chain instance and drops hash_mutex
> before returning.
>
> If a concurrent call to serial_unlink_irq_chain() runs immediately after
> serial_get_or_create_irq_info() returns while i->head is still NULL,
> serial_unlink_irq_chain() acquires hash_mutex, finds i with
> i->head == NULL, frees the chain structure via free_irq() / kfree(),
> and removes it from the hashtable. serial_link_irq_chain() then
> proceeds to scoped_guard(spinlock_irq, &i->lock), dereferencing the freed
> chain pointer i and causing a slab use-after-free.
>
> Move guard(mutex)(&hash_mutex) to the beginning of
> serial_link_irq_chain() and rename serial_get_or_create_irq_info() to
> serial_get_or_create_irq_info_locked() so hash_mutex is held across the
> entire lookup, linking, and error-path unlinking sequence.
>
> Tested in QEMU against tip of mainline (62f4c998b297, "Merge tag
> 'parisc-for-7.3-rc5' of git://git.kernel.org/.../parisc-linux")
> with KASAN enabled by concurrently opening/closing 8250 serial ports
> sharing IRQ 4 (ttyS0 and ttyS2): on the unfixed kernel KASAN detects
> slab-use-after-free in serial_link_irq_chain(); whereas with this fix
> applied, port registration and unregistration run cleanly with 0 KASAN
> warnings.
>
> Fixes: e91f1ed6c24f ("serial: 8250: fix use-after-free in serial_link_irq_chain")
> Cc: stable@vger.kernel.org
> Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> Assisted-by: LLM
> Signed-off-by: Hui Peng <benquike@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260930041216.155911-1-benquike@gmail.com?part=1
next prev parent reply other threads:[~2026-09-30 4:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 4:12 [PATCH v5 0/3] serial: fix IRQ chain race, baud fallback, and uartclk overflow Hui Peng
2026-09-30 4:12 ` [PATCH v5 1/3] serial: 8250: hold hash_mutex across IRQ chain linking in serial_link_irq_chain() Hui Peng
2026-09-30 4:19 ` sashiko-bot [this message]
2026-09-30 10:06 ` Ilpo Järvinen
2026-09-30 4:12 ` [PATCH v5 2/3] serial: core: allow third iteration in uart_get_baud_rate() fallback Hui Peng
2026-09-30 4:21 ` sashiko-bot
2026-09-30 4:12 ` [PATCH v5 3/3] serial: core: reject baud_base values that overflow port->uartclk in uart_set_info() Hui Peng
2026-09-30 4:19 ` sashiko-bot
2026-09-30 6:29 ` Jiri Slaby
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=20260930041931.C4AC61F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=benquike@gmail.com \
--cc=linux-serial@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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