8.4

CVE-2025-39790: debian debian_linux Double Free

CVSS: 8.4v3.1HighModified
AliasesUBUNTU-CVE-2025-39790DEBIAN-CVE-2025-39790
Published 11-09-2025Last modified 15-10-2026

Vulnerability summary

CVE-2025-39790 is a high (CVSS 8.4) Double Free vulnerability in debian debian_linux. EPSS estimates a 0.16% chance of exploitation in the next 30 days, higher than 4.8% of scored vulnerabilities.

Overall risk
34/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.4/10
010
High · v3.1 (CVE.org)
EPSS score
0.16%
0%100%
Low · +0.01 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 48 · Related 44

Timeline

  1. 11-09-2025
    PublishedVulnerability first disclosed.
  2. 15-10-2026
    Last modifiedVulnerability information updated.

Description

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]

CVSS metrics

5 scores · 4 sources · 2 versions

EPSS trend

Probability

0.16%

Chance of exploitation in the next 30 days

Percentile

5%

Versus all other CVEs

30-day change

+0.01 pp

From 0.16% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.16%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Ubuntu136 products
  • linux< 5.15.0-163.173 | < 6.8.0-100.100
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws< 5.15.0-1097.104 | < 6.8.0-1046.49
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian2 products
  • linux< 6.1.153-1 | < 6.12.48-1 | < 6.16.5-1
  • debian_linuxEOL11.0
Linux2 products
  • linux≥ 1d3173a3bae7039b765a0956e3e4bf846dbaacb8, < 7b3f0e3b60c27f4fcb69927d84987e5fd6240530 | ≥ 1d3173a3bae7039b765a0956e3e4bf846dbaacb8, < 4079c6c59705b96285219b9efc63cab870d757b7 | ≥ 1d3173a3bae7039b765a0956e3e4bf846dbaacb8, < 5e17429679a8545afe438ce7a82a13a54e8ceabb | ≥ 1d3173a3bae7039b765a0956e3e4bf846dbaacb8, < 2ec99b922f4661521927eeada76f431eebfbabc4 | ≥ 1d3173a3bae7039b765a0956e3e4bf846dbaacb8, < 44e1a079e18f78d6594a715b0c6d7e18c656f7b9 | ≥ 1d3173a3bae7039b765a0956e3e4bf846dbaacb8, < 5bd398e20f0833ae8a1267d4f343591a2dd20185 | 5.7
  • linux_kernel≥ 5.7, < 5.15.190 | ≥ 5.16, < 6.1.149 | ≥ 6.2, < 6.6.103 | ≥ 6.7, < 6.12.44 | ≥ 6.13, < 6.16.4

3 vendors · 140 products

References

37 links
Show all 37 references