Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-39870dmaengine: idxd: Fix double free in idxd_setup_wqs()

Description

In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix double free in idxd_setup_wqs() The clean up in idxd_setup_wqs() has had a couple bugs because the error handling is a bit subtle. It's simpler to just re-write it in a cleaner way. The issues here are: 1) If "idxd->max_wqs" is <= 0 then we call put_device(conf_dev) when "conf_dev" hasn't been initialized. 2) If kzalloc_node() fails then again "conf_dev" is invalid. It's either uninitialized or it points to the "conf_dev" from the previous iteration so it leads to a double free. It's better to free partial loop iterations within the loop and then the unwinding at the end can handle whole loop iterations. I also renamed the labels to describe what the goto does and not where the goto was located.

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-39870, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected d584acdf54f409cb7eae1359ae6c12aaabedeed8 – < 25e6146c2812487a88f619d5ff6efbdcd5b2bc31
    • affected 47846211998a9ffb0fcc08092eb95ac783d2b11a – < df82c7901513fd0fc738052a8e6a330d92cc8ec9
    • affected 5fcd392dae6d6aba7dc64ffdbb838ff191315da3 – < ec5430d090d0b6ace8fefa290fc37e88930017d2
    • affected 3fd2f4bc010cdfbc07dd21018dc65bd9370eb7a4 – < 9f0e225635475b2285b966271d5e82cba74295b1
    • affected 3fd2f4bc010cdfbc07dd21018dc65bd9370eb7a4 – < 39aaa337449e71a41d4813be0226a722827ba606
    • affected ed2c66000aa64c0d2621864831f0d04c820a1441
    • affected 6.1.140 – < 6.1.153
    • affected 6.6.92 – < 6.6.107
    • affected 6.12.30 – < 6.12.48
    • affected 6.14.8 – < 6.15
  • Linux · Linux

    • affected 6.15
    • unaffected < 6.15
    • unaffected 6.1.153 – ≤ 6.1.*
    • unaffected 6.6.107 – ≤ 6.6.*
    • unaffected 6.12.48 – ≤ 6.12.*
    • unaffected 6.16.8 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-39870 badge
[![CVE-2025-39870](https://cveledger.app/badge/CVE-2025-39870.svg)](https://cveledger.app/cve/CVE-2025-39870)

Record last updated .