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-71221dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue()

Description

In the Linux kernel, the following vulnerability has been resolved: dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() Add proper locking in mmp_pdma_residue() to prevent use-after-free when accessing descriptor list and descriptor contents. The race occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors: CPU 0 CPU 1 ----- ----- mmp_pdma_tx_status() mmp_pdma_residue() -> NO LOCK held list_for_each_entry(sw, ..) DMA interrupt dma_do_tasklet() -> spin_lock(&desc_lock) list_move(sw->node, ...) spin_unlock(&desc_lock) | dma_pool_free(sw) <- FREED! -> access sw->desc <- UAF! This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan > 1). Fix by protecting the chain_running list iteration and descriptor access with the chan->desc_lock spinlock.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 9 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-71221, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (19 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 1b38da264674d6a0fe26a63996b8f88b88c3da48 – < 3f0e0e2d9e752570041e95fd04635e2580097819
    • affected 1b38da264674d6a0fe26a63996b8f88b88c3da48 – < dfb5e05227745de43b7fd589721817a4337c970d
    • affected 1b38da264674d6a0fe26a63996b8f88b88c3da48 – < eba0c75670c022cb1f948600db972524bcfe8166
    • affected 1b38da264674d6a0fe26a63996b8f88b88c3da48 – < fc023b8fab057f0c910856ff36d3e12a30b7af4a
    • affected 1b38da264674d6a0fe26a63996b8f88b88c3da48 – < 9f665b3c3d9a168410251f27a5d019b7bf93185c
    • affected 1b38da264674d6a0fe26a63996b8f88b88c3da48 – < a143545855bc2c6e1330f6f57ae375ac44af00a7
  • Linux · Linux

    • affected 3.16
    • unaffected < 3.16
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.78 – ≤ 6.12.*
    • unaffected 6.18.10 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .