Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 069fd1688c57c0cc8a3de64d108579b31676f74b, 1baed10553fc8b388351d8fc803e3ae6f1a863bc, 301a96cc4dc006c9a285913d301e681cfbf7edb6.

Low priority for now. Upgrade to Linux Linux 069fd1688c57c0cc8a3de64d108579b31676f74b, 1baed10553fc8b388351d8fc803e3ae6f1a863bc, 301a96cc4dc006c9a285913d301e681cfbf7edb6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Sep 23, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
7.1
CNA · Linux
8.4
1.3 point gap

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-39869

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • linux linux kernel5.5 and later · before 5.10.245
  • linux linux kernel5.11 and later · before 5.15.194
  • linux linux kernel5.16 and later · before 6.1.153
  • linux linux kernel4.4 and later · before 5.4.300
  • linux linux kernel6.7 and later · before 6.12.48
  • linux linux kernel6.13 and later · before 6.16.8
  • linux linux kernel6.2 and later · before 6.6.107
  • linux linux kernel6.17

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.4affected
    • 2b6b3b7420190888793c49e97276e1e73bd7eaed and later · before 7d4de60d6db02d9b01d5890d5156b04fad65d07aaffected · git
    • 2b6b3b7420190888793c49e97276e1e73bd7eaed and later · before d722de80ce037dccf6931e778f4a46499d51bdf9affected · git
    • 2b6b3b7420190888793c49e97276e1e73bd7eaed and later · before 301a96cc4dc006c9a285913d301e681cfbf7edb6affected · git
    • 2b6b3b7420190888793c49e97276e1e73bd7eaed and later · before 5e462fa0dfdb52b3983cf41532d3d4c7d63e2f93affected · git
    • 2b6b3b7420190888793c49e97276e1e73bd7eaed and later · before 1baed10553fc8b388351d8fc803e3ae6f1a863bcaffected · git
    • 2b6b3b7420190888793c49e97276e1e73bd7eaed and later · before 069fd1688c57c0cc8a3de64d108579b31676f74baffected · git
    • 2b6b3b7420190888793c49e97276e1e73bd7eaed and later · before d5e82f3f2c918d446df46e8d65f8083fd97cdec5affected · git
    • 2b6b3b7420190888793c49e97276e1e73bd7eaed and later · before e63419dbf2ceb083c1651852209c7f048089ac0faffected · git
    • before 4.4not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11linuxbefore 5.10.247-15.10.247-1
Debian:12linuxbefore 6.1.153-16.1.153-1
Debian:13linuxbefore 6.12.48-16.12.48-1
Debian:14linuxbefore 6.16.8-16.16.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-39866Sep 19, 2025 · fs: writeback: fix use-after-free in __mark_inode_dirty()
    31Monitor
  • ← EarlierCVE-2025-39868Sep 23, 2025 · erofs: fix runtime warning on truncate_folio_batch_exceptionals()
    31Monitor
  • Later →CVE-2025-39870Sep 23, 2025 · dmaengine: idxd: Fix double free in idxd_setup_wqs()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux069fd1688c57c0cc8a3de64d108579b31676f74bVendor (CNA)
Linux Linux1baed10553fc8b388351d8fc803e3ae6f1a863bcVendor (CNA)
Linux Linux301a96cc4dc006c9a285913d301e681cfbf7edb6Vendor (CNA)
Linux Linux5e462fa0dfdb52b3983cf41532d3d4c7d63e2f93Vendor (CNA)
Linux Linux7d4de60d6db02d9b01d5890d5156b04fad65d07aVendor (CNA)
Linux Linuxd5e82f3f2c918d446df46e8d65f8083fd97cdec5Vendor (CNA)
Linux Linuxd722de80ce037dccf6931e778f4a46499d51bdf9Vendor (CNA)
Linux Linuxe63419dbf2ceb083c1651852209c7f048089ac0fVendor (CNA)
debian:linux6.1.153-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records