Linux Serial subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Sebastian Alba Vives" <sebasjosue84@gmail.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH 1/2] serial: sifive: fix NULL pointer dereference in probe IRQ window
Date: Sat, 17 Oct 2026 07:51:13 +0000	[thread overview]
Message-ID: <sashiko-outbox-175374@kernel.org> (raw)
In-Reply-To: <20261017074453.62645-2-sebasjosue84@gmail.com>

> From: Sebastian Alba <sebasjosue84@estudiantec.cr>
> 
> sifive_serial_probe() installs the interrupt handler with request_irq()
> before uart_add_one_port() has run.  uart_add_one_port() is what assigns
> ssp->port.state, and ssp is allocated with devm_kzalloc(), so
> ssp->port.state is NULL for the whole window between the two calls.
> 
> The handler dereferences that pointer unconditionally:
> 
>   sifive_serial_irq()
>     __ssp_receive_chars()
>       uart_insert_char(&ssp->port, ...)        /* port->state->port */
>       tty_flip_buffer_push(&ssp->port.state->port);
> 
> so an RX interrupt taken inside the window oopses the kernel.
> [ ... ]
> left there.  Unwinding is adjusted accordingly: uart_remove_one_port()
> now balances the added port on the request_irq() failure path.
> 
> Fixes: 45c054d0815b ("tty: serial: add driver for the SiFive UART")
> Signed-off-by: Sebastian Alba <sebasjosue84@estudiantec.cr>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261017074453.62645-1-sebasjosue84@gmail.com?part=1


  reply	other threads:[~2026-10-17  7:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17  7:44 [PATCH 0/2] serial: sifive: fix two init ordering bugs in probe Sebastian Alba Vives
2026-10-17  7:44 ` [PATCH 1/2] serial: sifive: fix NULL pointer dereference in probe IRQ window Sebastian Alba Vives
2026-10-17  7:51   ` sashiko-bot [this message]
2026-10-17  7:44 ` [PATCH 2/2] serial: sifive: avoid division by zero in the clock notifier Sebastian Alba Vives
2026-10-17  7:47   ` sashiko-bot

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=sashiko-outbox-175374@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=sebasjosue84@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