CVE-2025-71221

HIGHNVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-02-14. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
36(Track)
EG Risk 36/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.8%
KEV
Not listed

Published

February 14, 2026

Last Modified

July 14, 2026

Advisory Details (8)

Auto-updated Jul 14, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic🔴 Active Exploitation

SSA-082556

https://cert-portal.siemens.com/productcert/html/ssa-082556.html
generic

SSA-019113

https://cert-portal.siemens.com/productcert/html/ssa-019113.html
generic

dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fc023b8fab057f0c910856ff36d3e12a30b7af4a
generic

dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eba0c75670c022cb1f948600db972524bcfe8166
generic

dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dfb5e05227745de43b7fd589721817a4337c970d
generic

dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a143545855bc2c6e1330f6f57ae375ac44af00a7
generic

dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f665b3c3d9a168410251f27a5d019b7bf93185c
generic

dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f0e0e2d9e752570041e95fd04635e2580097819

Vendor Advisories for CVE-2025-71221(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.15.209—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 03:03 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-17 14:29 UTCOSV refresh
  8. 2026-07-16 17:02 UTCEPSS rescore
  9. 2026-07-16 17:02 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-14 13:19 UTCNVD updateCVSS v3 → 7 · severity → HIGH
  13. 2026-07-14 13:11 UTCMITRE cvelistV5
  14. 2026-07-13 06:12 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-08 15:15 UTCEPSS rescore
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-01 15:06 UTCEPSS rescore
Show 52 more
  1. 2026-06-30 23:22 UTCEPSS rescore
  2. 2026-06-30 23:22 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-29 14:06 UTCEPSS rescore
  5. 2026-06-29 13:02 UTCOSV refresh
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-28 14:07 UTCEPSS rescore
  8. 2026-06-24 14:05 UTCEPSS rescore
  9. 2026-06-24 14:04 UTCEPSS rescore
  10. 2026-06-23 21:32 UTCEPSS rescore
  11. 2026-06-21 01:59 UTCEPSS rescore
  12. 2026-06-21 01:59 UTCEPSS rescore
  13. 2026-06-17 17:53 UTCEPSS rescore
  14. 2026-06-16 17:52 UTCEPSS rescore
  15. 2026-06-15 17:48 UTCEPSS rescore
  16. 2026-06-14 23:18 UTCEPSS rescore
  17. 2026-06-13 23:00 UTCEPSS rescore
  18. 2026-06-13 23:00 UTCEPSS rescore
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-06-12 23:12 UTCEPSS rescore
  21. 2026-06-12 03:36 UTCGHSA enrichment
  22. 2026-06-11 14:00 UTCEPSS rescore
  23. 2026-06-10 22:18 UTCEPSS rescore
  24. 2026-06-10 21:22 UTCGHSA enrichment
  25. 2026-06-10 13:22 UTCEPSS rescore
  26. 2026-06-10 09:37 UTCGHSA enrichment
  27. 2026-06-09 19:45 UTCGHSA enrichment
  28. 2026-06-08 14:17 UTCEPSS rescore
  29. 2026-06-08 14:17 UTCEPSS rescore
  30. 2026-06-08 05:10 UTCGHSA enrichment
  31. 2026-06-07 17:55 UTCGHSA enrichment
  32. 2026-06-07 15:24 UTCEPSS rescore
  33. 2026-06-07 15:24 UTCEPSS rescore
  34. 2026-06-06 13:47 UTCEPSS rescore
  35. 2026-06-06 13:47 UTCEPSS rescore
  36. 2026-06-05 22:47 UTCEPSS rescore
  37. 2026-06-05 22:46 UTCEPSS rescore
  38. 2026-06-05 06:10 UTCEPSS rescore
  39. 2026-06-05 06:10 UTCEPSS rescore
  40. 2026-06-04 13:12 UTCEPSS rescore
  41. 2026-06-04 13:12 UTCEPSS rescore
  42. 2026-06-02 20:13 UTCEPSS rescore
  43. 2026-06-01 13:51 UTCEPSS rescore
  44. 2026-06-01 13:51 UTCEPSS rescore
  45. 2026-05-31 22:30 UTCEPSS rescore
  46. 2026-05-31 22:30 UTCEPSS rescore
  47. 2026-05-31 00:16 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-29 13:51 UTCEG score recompute
  50. 2026-05-29 13:51 UTCGHSA enrichment
  51. 2026-05-29 13:44 UTCEPSS rescore
  52. 2026-05-29 13:44 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-71221?
CVE-2025-71221 is a high vulnerability published on February 14, 2026. In the Linux kernel, the following vulnerability has been resolved: dmaengine: mmppdma: Fix race condition in mmppdma_residue() Add proper locking in mmppdmaresidue() to prevent use-after-free when accessing descriptor list and descriptor contents. The race occurs when multiple threads call…
When was CVE-2025-71221 disclosed?
CVE-2025-71221 was first published in the National Vulnerability Database on February 14, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71221 actively exploited?
CVE-2025-71221 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-71221?
CVE-2025-71221 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2025-71221?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71221, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-71221

Explore →

Is Your Infrastructure Affected by CVE-2025-71221?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs