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-39869dmaengine: ti: edma: Fix memory allocation size for queue_priority_map

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 11 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-39869, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.4CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% 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 8.4.

Affected products

  • Linux · Linux

    • affected 2b6b3b7420190888793c49e97276e1e73bd7eaed – < 7d4de60d6db02d9b01d5890d5156b04fad65d07a
    • affected 2b6b3b7420190888793c49e97276e1e73bd7eaed – < d722de80ce037dccf6931e778f4a46499d51bdf9
    • affected 2b6b3b7420190888793c49e97276e1e73bd7eaed – < 301a96cc4dc006c9a285913d301e681cfbf7edb6
    • affected 2b6b3b7420190888793c49e97276e1e73bd7eaed – < 5e462fa0dfdb52b3983cf41532d3d4c7d63e2f93
    • affected 2b6b3b7420190888793c49e97276e1e73bd7eaed – < 1baed10553fc8b388351d8fc803e3ae6f1a863bc
    • affected 2b6b3b7420190888793c49e97276e1e73bd7eaed – < 069fd1688c57c0cc8a3de64d108579b31676f74b
    • affected 2b6b3b7420190888793c49e97276e1e73bd7eaed – < d5e82f3f2c918d446df46e8d65f8083fd97cdec5
    • affected 2b6b3b7420190888793c49e97276e1e73bd7eaed – < e63419dbf2ceb083c1651852209c7f048089ac0f
  • Linux · Linux

    • affected 4.4
    • unaffected < 4.4
    • unaffected 5.4.300 – ≤ 5.4.*
    • unaffected 5.10.245 – ≤ 5.10.*
    • unaffected 5.15.194 – ≤ 5.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

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .