CVE-2025-39790

In the Linux kernel, the following vulnerability has been resolved: 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. [mani: added stable tag and reworded commit message]

• CWE-415

• https://git.kernel.org/stable/c/2ec99b922f4661521927eeada76f431eebfbabc4Patch
• https://git.kernel.org/stable/c/4079c6c59705b96285219b9efc63cab870d757b7Patch
• https://git.kernel.org/stable/c/44e1a079e18f78d6594a715b0c6d7e18c656f7b9Patch
• https://git.kernel.org/stable/c/5bd398e20f0833ae8a1267d4f343591a2dd20185Patch
• https://git.kernel.org/stable/c/5e17429679a8545afe438ce7a82a13a54e8ceabbPatch
• https://git.kernel.org/stable/c/7b3f0e3b60c27f4fcb69927d84987e5fd6240530Patch
• https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlThird Party Advisory
• https://cert-portal.siemens.com/productcert/html/ssa-032379.html

Published

Sep 11, 2025

Last Modified

Jul 30, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2025-39785In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39786In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2025-39787In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39788In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-39789In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-3979A vulnerability classified as problematic has been found in …6.5
• CVE-2025-39791In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39792In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39793In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-39794In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39795In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39796In the Linux kernel, the following vulnerability has been re…7.8