CVE-2025-39869

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2025-09-23. NVD baseline CVSS 7.1; sources differ by 0.0.

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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

dmaengine: ti: edma: Fix memory allocation size for queue_priority_map

Fix a critical memory allocation bug in edma_setup_from_hw() where queue_priority_map was allocated with insufficient memory. The code declared queue_priority_map as s8 (*)[2] (pointer to array of 2 s8), but allocated memory using sizeof(s8) instead of the correct size.

This caused out-of-bounds memory writes when accessing: queue_priority_map[i][0] = i; queue_priority_map[i][1] = i;

The bug manifested as kernel crashes with "Oops - undefined instruction" on ARM platforms (BeagleBoard-X15) during EDMA driver probe, as the memory corruption triggered kernel hardening features on Clang.

Change the allocation to use sizeof(*queue_priority_map) which automatically gets the correct size for the 2D array structure.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

September 23, 2025

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 2, 2026
Patch available.
generic Patch Available

[SECURITY] [DLA 4328-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
generic

dmaengine: ti: edma: Fix memory allocation size for queue_priority_map - kernel/git/stable/linux.git - Linux kernel stable tree

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

dmaengine: ti: edma: Fix memory allocation size for queue_priority_map - kernel/git/stable/linux.git - Linux kernel stable tree

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

dmaengine: ti: edma: Fix memory allocation size for queue_priority_map - kernel/git/stable/linux.git - Linux kernel stable tree

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

dmaengine: ti: edma: Fix memory allocation size for queue_priority_map - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d4de60d6db02d9b01d5890d5156b04fad65d07a
generic

dmaengine: ti: edma: Fix memory allocation size for queue_priority_map - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5e462fa0dfdb52b3983cf41532d3d4c7d63e2f93
generic

dmaengine: ti: edma: Fix memory allocation size for queue_priority_map - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/301a96cc4dc006c9a285913d301e681cfbf7edb6
generic

dmaengine: ti: edma: Fix memory allocation size for queue_priority_map - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1baed10553fc8b388351d8fc803e3ae6f1a863bc
generic

dmaengine: ti: edma: Fix memory allocation size for queue_priority_map - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/069fd1688c57c0cc8a3de64d108579b31676f74b

Vendor Advisories for CVE-2025-39869(1)

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

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.170.159) @ jammy2026-07-30ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1100.107~20.04.1) @ focal2026-07-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-07-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-07-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1052.52) @ jammy2026-07-30ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1100.90) @ jammy2026-07-30ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1099.103) @ jammy2026-07-30ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1097.93) @ jammy2026-07-30ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1095.101~20.04.1) @ focal2026-07-30ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1095.95) @ jammy2026-07-30ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1041.43) @ jammy2026-07-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1095.95) @ jammy2026-07-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-07-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-07-30ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-07-30ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-07-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-07-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-07-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-07-30ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-07-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-07-30ubuntu
linuxKernel @ 5.4.300osv

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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (47 versions)5.10.247-1
linux-6.16.1.106-3~deb11u1 ... 6.1.148-1~deb11u1 (11 versions)6.1.153-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (43 versions)6.1.153-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1, 6.12.41-1, 6.12.43-1, 6.12.43-1~bpo12+16.12.48-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (66 versions)6.16.8-1

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 24× 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.

Showing the most recent 100 of 140 total refreshes for this CVE.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:29 UTCEPSS rescore
  4. 2026-09-16 14:07 UTCEPSS rescore
  5. 2026-09-16 05:14 UTCEPSS rescore
  6. 2026-09-13 16:46 UTCEPSS rescore
  7. 2026-09-12 15:00 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-11 09:35 UTCEPSS rescore
  10. 2026-09-10 09:33 UTCEPSS rescore
  11. 2026-09-08 21:59 UTCEPSS rescore
  12. 2026-09-07 16:00 UTCEPSS rescore
  13. 2026-09-07 11:18 UTCOSV refresh
  14. 2026-09-06 13:46 UTCEPSS rescore
  15. 2026-09-04 05:05 UTCEPSS rescore
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:38 UTCEPSS rescore
  19. 2026-08-30 19:16 UTCEPSS rescore
  20. 2026-08-30 01:21 UTCEPSS rescore
  21. 2026-08-28 21:40 UTCEPSS rescore
  22. 2026-08-27 14:24 UTCEPSS rescore
  23. 2026-08-26 14:45 UTCEPSS rescore
  24. 2026-08-25 13:48 UTCEPSS rescore
  25. 2026-08-23 00:18 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 23:48 UTCEPSS rescore
  2. 2026-08-20 22:54 UTCEPSS rescore
  3. 2026-08-20 20:31 UTCOSV refresh
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 13:47 UTCEPSS rescore
  7. 2026-08-17 13:46 UTCEPSS rescore
  8. 2026-08-16 14:55 UTCEPSS rescore
  9. 2026-08-16 02:13 UTCEPSS rescore
  10. 2026-08-15 01:29 UTCEPSS rescore
  11. 2026-08-13 21:59 UTCEPSS rescore
  12. 2026-08-12 13:50 UTCEPSS rescore
  13. 2026-08-09 13:46 UTCEPSS rescore
  14. 2026-08-07 16:26 UTCEPSS rescore
  15. 2026-08-06 13:46 UTCEPSS rescore
  16. 2026-08-05 12:56 UTCEG score recompute
  17. 2026-08-05 12:56 UTCVendor advisory
  18. 2026-08-05 12:56 UTCGHSA enrichment
  19. 2026-08-04 15:09 UTCEPSS rescore
  20. 2026-08-04 10:37 UTCEPSS rescore
  21. 2026-08-03 10:35 UTCEPSS rescore
  22. 2026-08-02 02:26 UTCEPSS rescore
  23. 2026-08-01 04:15 UTCEPSS rescore
  24. 2026-07-30 16:27 UTCEPSS rescore
  25. 2026-07-30 06:51 UTCEG score recompute
  26. 2026-07-30 06:51 UTCVendor advisory
  27. 2026-07-30 06:51 UTCGHSA enrichment
  28. 2026-07-30 01:29 UTCEPSS rescore
  29. 2026-07-28 15:35 UTCEPSS rescore
  30. 2026-07-26 14:54 UTCEPSS rescore
  31. 2026-07-23 19:11 UTCOSV refresh
  32. 2026-07-23 02:55 UTCEG score recompute
  33. 2026-07-22 14:07 UTCEPSS rescore
  34. 2026-07-22 14:07 UTCEPSS rescore
  35. 2026-07-21 15:24 UTCEPSS rescore
  36. 2026-07-20 17:07 UTCEPSS rescore
  37. 2026-07-19 14:30 UTCEPSS rescore
  38. 2026-07-19 14:30 UTCEPSS rescore
  39. 2026-07-18 10:04 UTCEPSS rescore
  40. 2026-07-18 10:04 UTCEPSS rescore
  41. 2026-07-16 17:02 UTCEPSS rescore
  42. 2026-07-15 16:57 UTCEPSS rescore
  43. 2026-07-15 16:57 UTCEPSS rescore
  44. 2026-07-15 01:59 UTCEPSS rescore
  45. 2026-07-15 01:59 UTCEPSS rescore
  46. 2026-07-13 22:29 UTCEPSS rescore
  47. 2026-07-13 22:29 UTCEPSS rescore
  48. 2026-07-13 06:12 UTCEPSS rescore
  49. 2026-07-12 05:46 UTCEPSS rescore
  50. 2026-07-11 08:27 UTCEPSS rescore
  51. 2026-07-11 08:27 UTCEPSS rescore
  52. 2026-07-09 19:09 UTCEPSS rescore
  53. 2026-07-09 19:09 UTCEPSS rescore
  54. 2026-07-07 13:45 UTCEPSS rescore
  55. 2026-07-06 13:41 UTCOSV refresh
  56. 2026-07-06 02:23 UTCEPSS rescore
  57. 2026-07-05 02:30 UTCEPSS rescore
  58. 2026-07-04 06:30 UTCEPSS rescore
  59. 2026-07-01 15:06 UTCEPSS rescore
  60. 2026-07-01 15:06 UTCEPSS rescore
  61. 2026-06-30 23:22 UTCEPSS rescore
  62. 2026-06-30 23:22 UTCEPSS rescore
  63. 2026-06-29 14:06 UTCEPSS rescore
  64. 2026-06-29 14:06 UTCEPSS rescore
  65. 2026-06-28 14:07 UTCEPSS rescore
  66. 2026-06-28 14:07 UTCEPSS rescore
  67. 2026-06-28 04:55 UTCEPSS rescore
  68. 2026-06-28 04:55 UTCEPSS rescore
  69. 2026-06-27 03:08 UTCEPSS rescore
  70. 2026-06-27 03:08 UTCEPSS rescore
  71. 2026-06-25 13:49 UTCEPSS rescore
  72. 2026-06-25 13:49 UTCEPSS rescore
  73. 2026-06-24 14:04 UTCEPSS rescore
  74. 2026-06-24 14:04 UTCEPSS rescore
  75. 2026-06-23 21:32 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-39869?
CVE-2025-39869 is a high vulnerability published on September 23, 2025. In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: edma: Fix memory allocation size for queueprioritymap Fix a critical memory allocation bug in edmasetupfrom_hw() where queueprioritymap was allocated with insufficient memory. The code declared queueprioritymap as s8…
When was CVE-2025-39869 disclosed?
CVE-2025-39869 was first published in the National Vulnerability Database on September 23, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-39869 actively exploited?
CVE-2025-39869 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.4% of all scored CVEs.
What is the CVSS score of CVE-2025-39869?
CVE-2025-39869 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2025-39869?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-39869, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-39869

Explore →

Is Your Infrastructure Affected by CVE-2025-39869?

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