FAILED: patch "[PATCH] bus: mhi: host: Detect events pointing to unexpected TREs" failed to apply to 5.15-stable tree
Subsystems (2)
[email protected]
maintainerThe patch below does not apply to the 5.15-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
To reproduce the conflict and resubmit, you may use the following commands:
git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-5.15.y
git checkout FETCH_HEAD
git cherry-pick -x 5bd398e20f0833ae8a1267d4f343591a2dd20185
# <resolve conflicts, build, test, etc.>
git commit -s
git send-email --to '<[email protected]>' --in-reply-to '2025082132-hurricane-stank-2ae5@gregkh' --subject-prefix 'PATCH 5.15.y' HEAD^..
Possible dependencies:
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From 5bd398e20f0833ae8a1267d4f343591a2dd20185 Mon Sep 17 00:00:00 2001
From: Youssef Samir <[email protected]>
Date: Mon, 14 Jul 2025 18:30:39 +0200
Subject: [PATCH] bus: mhi: host: Detect events pointing to unexpected TREs
When a remote device sends a completion event to the host, it contains a pointer to the consumed TRE. The host uses this pointer to process all of the TREs between it and the host's local copy of the ring's read pointer. This works when processing completion for chained transactions, but can lead to nasty results if the device sends an event for a single-element transaction with a read pointer that is multiple elements ahead of the host's read pointer.
For instance, if the host accesses an event ring while the device is updating it, the pointer inside of the event might still point to an old TRE. If the host uses the channel's xfer_cb() to directly free the buffer pointed to by the TRE, the buffer will be double-freed.
This behavior was observed on an ep that used upstream EP stack without 'commit 6f18d174b73d ("bus: mhi: ep: Update read pointer only after buffer is written")'. Where the device updated the events ring pointer before updating the event contents, so it left a window where the host was able to access the stale data the event pointed to, before the device had the chance to update them. The usual pattern was that the host received an event pointing to a TRE that is not immediately after the last processed one, so it got treated as if it was a chained transaction, processing all of the TREs in between the two read pointers.
This commit aims to harden the host by ensuring transactions where the event points to a TRE that isn't local_rp + 1 are chained.
drivers/bus/mhi/host/main.c +11 -1
@@ -602,7 +602,7 @@ static int parse_xfer_event(struct mhi_controller *mhi_cntrl, {dma_addr_t ptr =MHI_TRE_GET_EV_PTR (event);struct mhi_ring_element *local_rp, *ev_tre; -void *dev_rp; +void *dev_rp, *next_rp;struct mhi_buf_info *buf_info;u16 xfer_len;
@@ -621,6 +621,16 @@ static int parse_xfer_event(struct mhi_controller *mhi_cntrl, result.dir = mhi_chan->dir; local_rp = tre_ring->rp; + + next_rp = local_rp +1 ; +if (next_rp >= tre_ring->base + tre_ring->len) + next_rp = tre_ring->base; +if (dev_rp != next_rp && !MHI_TRE_DATA_GET_CHAIN (local_rp)) { +dev_err (&mhi_cntrl->mhi_dev->dev, +"Event element points to an unexpected TRE\n" ); +break ; + } +while (local_rp != dev_rp) { buf_info = buf_ring->rp;/* If it's the last TRE, get length from the event */
Sasha Levin
maintainerPATCH 1/1 bus: mhi: host: Detect events pointing to unexpected TREs
From: Youssef Samir <[email protected]>
[ Upstream commit 5bd398e20f0833ae8a1267d4f343591a2dd20185 ]
When a remote device sends a completion event to the host, it contains a pointer to the consumed TRE. The host uses this pointer to process all of the TREs between it and the host's local copy of the ring's read pointer. This works when processing completion for chained transactions, but can lead to nasty results if the device sends an event for a single-element transaction with a read pointer that is multiple elements ahead of the host's read pointer.
For instance, if the host accesses an event ring while the device is updating it, the pointer inside of the event might still point to an old TRE. If the host uses the channel's xfer_cb() to directly free the buffer pointed to by the TRE, the buffer will be double-freed.
This behavior was observed on an ep that used upstream EP stack without 'commit 6f18d174b73d ("bus: mhi: ep: Update read pointer only after buffer is written")'. Where the device updated the events ring pointer before updating the event contents, so it left a window where the host was able to access the stale data the event pointed to, before the device had the chance to update them. The usual pattern was that the host received an event pointing to a TRE that is not immediately after the last processed one, so it got treated as if it was a chained transaction, processing all of the TREs in between the two read pointers.
This commit aims to harden the host by ensuring transactions where the event points to a TRE that isn't local_rp + 1 are chained.
--- drivers/bus/mhi/host/main.c | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-)
drivers/bus/mhi/host/main.c +14 -1
@@ -594,7 +594,7 @@ static int parse_xfer_event(struct mhi_controller *mhi_cntrl, {dma_addr_t ptr =MHI_TRE_GET_EV_PTR (event);struct mhi_ring_element *local_rp, *ev_tre; -void *dev_rp; +void *dev_rp, *next_rp;struct mhi_buf_info *buf_info;u16 xfer_len;
@@ -613,6 +613,19 @@ static int parse_xfer_event(struct mhi_controller *mhi_cntrl, result.dir = mhi_chan->dir; local_rp = tre_ring->rp; + + next_rp = local_rp +1 ; +if (next_rp >= tre_ring->base + tre_ring->len) + next_rp = tre_ring->base; +/* Check if the event points to an unexpected TRE. +* Chain flag is bit 0 of dword[1] in the TRE. +*/ +if (dev_rp != next_rp && !(le32_to_cpu (local_rp->dword[1 ]) &0x1 )) { +dev_err (&mhi_cntrl->mhi_dev->dev, +"Event element points to an unexpected TRE\n" ); +break ; + } +while (local_rp != dev_rp) { buf_info = buf_ring->rp;/* If it's the last TRE, get length from the event */
Signature · 1 line
2.50.1