From: Austin Schlegel via B4 Relay <devnull+schlegelas.outlook.com@kernel.org>
To: Laxman Dewangan <ldewangan@nvidia.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Alan Cox <alan@linux.intel.com>,
Stephen Warren <swarren@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-tegra@vger.kernel.org,
Austin Schlegel <austin.schlegel@arthrex.com>,
Austin Schlegel <schlegelas@outlook.com>,
stable@vger.kernel.org
Subject: [PATCH v3 2/3] serial: tegra: fix TX DMA descriptor use-after-free
Date: Thu, 22 Oct 2026 17:10:25 -0400 [thread overview]
Message-ID: <20261022-serial-tegra-dma-uaf-v3-2-129f6d67f673@outlook.com> (raw)
In-Reply-To: <20261022-serial-tegra-dma-uaf-v3-0-129f6d67f673@outlook.com>
From: Austin Schlegel <schlegelas@outlook.com>
tegra_uart_stop_tx() calls dmaengine_terminate_all() and then
async_tx_ack(tup->tx_dma_desc) on the descriptor that was just
terminated. With the GPC DMA driver, dmaengine_terminate_all() frees
the active descriptor immediately, so the ack call that follows
touches freed memory.
This is the same use-after-free pattern fixed for the RX path in
tegra_uart_terminate_rx_dma() ("serial: tegra: fix RX DMA descriptor
use-after-free"). dmaengine clients must not touch a descriptor once
dmaengine_terminate_all() has returned.
Move the ack before dmaengine_terminate_all(), while the descriptor
is still valid.
tegra_uart_flush_buffer() reaches the same freed descriptor by another
route. It terminates the TX channel but leaves tx_in_progress set to
TEGRA_UART_TX_DMA, so a later tegra_uart_stop_tx() still sees a DMA
transfer in flight and acks the descriptor that
dmaengine_terminate_all() freed. Ack the descriptor before terminating
there too, and clear tx_in_progress so that nothing touches it
afterwards. Only clear it for a DMA transfer: a PIO transfer still has
the THRI interrupt enabled and is finished by the ISR.
Acking before terminating keeps descriptors reusable on APB DMA, which
only recycles a descriptor once it has been acked.
Found by code inspection while fixing the analogous RX bug and through
Sashiko automated review (see Link below); not reproduced on hardware,
since triggering it requires stopping or flushing an in-flight TX DMA
transfer at the right moment.
The ordering has been wrong since the driver was added; it became a
use-after-free once serial-tegra could use the GPC DMA driver,
which frees descriptors on terminate.
Fixes: e9ea096dd225 ("serial: tegra: add serial driver")
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/all/sashiko-outbox-172211@kernel.org/
Assisted-by: LLM
Signed-off-by: Austin Schlegel <schlegelas@outlook.com>
---
v3:
- Also fix tegra_uart_flush_buffer(), which terminated the TX channel
without clearing tx_in_progress, so a later tegra_uart_stop_tx()
acked the freed descriptor (reported by Sashiko review of v2
https://lore.kernel.org/all/sashiko-outbox-172211@kernel.org/).
- The tegra_uart_tx_dma_complete() race reported in the same review
is fixed separately in new patch 3/3.
v2:
- Reworded commit: Removed inaccurate flush example
- Switched to personal email (v1 sent from austin.schlegel@arthrex.com)
v1: https://lore.kernel.org/all/20261001-tty-linus-v1-2-ecb8576c802d@arthrex.com/
---
drivers/tty/serial/serial-tegra.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/tty/serial/serial-tegra.c b/drivers/tty/serial/serial-tegra.c
index a23a92cebe0d..c179a09b8fe2 100644
--- a/drivers/tty/serial/serial-tegra.c
+++ b/drivers/tty/serial/serial-tegra.c
@@ -639,9 +639,9 @@ static void tegra_uart_stop_tx(struct uart_port *u)
dmaengine_pause(tup->tx_dma_chan);
dmaengine_tx_status(tup->tx_dma_chan, tup->tx_cookie, &state);
+ async_tx_ack(tup->tx_dma_desc);
dmaengine_terminate_all(tup->tx_dma_chan);
count = tup->tx_bytes_requested - state.residue;
- async_tx_ack(tup->tx_dma_desc);
uart_xmit_advance(&tup->uport, count);
tup->tx_in_progress = 0;
}
@@ -1275,8 +1275,14 @@ static void tegra_uart_flush_buffer(struct uart_port *u)
struct tegra_uart_port *tup = to_tegra_uport(u);
tup->tx_bytes = 0;
- if (tup->tx_dma_chan)
+ if (tup->tx_dma_chan) {
+ if (tup->tx_in_progress == TEGRA_UART_TX_DMA) {
+ async_tx_ack(tup->tx_dma_desc);
+ tup->tx_in_progress = 0;
+ }
+
dmaengine_terminate_all(tup->tx_dma_chan);
+ }
}
static void tegra_uart_shutdown(struct uart_port *u)
--
2.53.0
next prev parent reply other threads:[~2026-10-22 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 21:10 [PATCH v3 0/3] serial: tegra: fix DMA descriptor use-after-free and stale completions Austin Schlegel via B4 Relay
2026-10-22 21:10 ` [PATCH v3 1/3] serial: tegra: fix RX DMA descriptor use-after-free Austin Schlegel via B4 Relay
2026-10-22 21:10 ` Austin Schlegel via B4 Relay [this message]
2026-10-22 21:10 ` [PATCH v3 3/3] serial: tegra: ignore stale DMA completion callbacks Austin Schlegel via B4 Relay
2026-10-27 6:52 ` [PATCH v3 0/3] serial: tegra: fix DMA descriptor use-after-free and stale completions Karl Mehltretter
2026-10-30 14:42 ` Austin Schlegel
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=20261022-serial-tegra-dma-uaf-v3-2-129f6d67f673@outlook.com \
--to=devnull+schlegelas.outlook.com@kernel.org \
--cc=alan@linux.intel.com \
--cc=austin.schlegel@arthrex.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=schlegelas@outlook.com \
--cc=stable@vger.kernel.org \
--cc=swarren@nvidia.com \
--cc=thierry.reding@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
all inboxes | Powered by JetHome®