CVE-2025-39870: dmaengine: idxd: Fix double free in idxd_setup_wqs()
Noroxi assessment
Priority: Monitor (action score 31/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.15% (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 25e6146c2812487a88f619d5ff6efbdcd5b2bc31, 39aaa337449e71a41d4813be0226a722827ba606, 6.1.153.
Low priority for now. Upgrade to Linux Linux 25e6146c2812487a88f619d5ff6efbdcd5b2bc31, 39aaa337449e71a41d4813be0226a722827ba606, 6.1.153 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: idxd: Fix double free in idxd_setup_wqs() The clean up in idxd_setup_wqs() has had a couple bugs because the error handling is a bit subtle. It's simpler to just re-write it in a cleaner way. The issues here are: 1) If "idxd->max_wqs" is <= 0 then we call put_device(conf_dev) when "conf_dev" hasn't been initialized. 2) If kzalloc_node() fails then again "conf_dev" is invalid. It's either uninitialized or it points to the "conf_dev" from the previous iteration so it leads to a double free. It's better to free partial loop iterations within the loop and then the unwinding at the end can handle whole loop iterations. I also renamed the labels to describe what the goto does and not where the goto was located.
- Published
- Sep 23, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-415
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_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 kernel6.6.92 and later · before 6.6.107
- linux linux kernel6.12.30 and later · before 6.12.48
- linux linux kernel6.14.8 and later · before 6.15
- linux linux kernel6.1.140 and later · before 6.1.153
- linux linux kernel6.15.1 and later · before 6.16.8
- linux linux kernel6.15
- 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
- ed2c66000aa64c0d2621864831f0d04c820a1441, 6.15affected
- d584acdf54f409cb7eae1359ae6c12aaabedeed8 and later · before 25e6146c2812487a88f619d5ff6efbdcd5b2bc31affected · git
- 47846211998a9ffb0fcc08092eb95ac783d2b11a and later · before df82c7901513fd0fc738052a8e6a330d92cc8ec9affected · git
- 5fcd392dae6d6aba7dc64ffdbb838ff191315da3 and later · before ec5430d090d0b6ace8fefa290fc37e88930017d2affected · git
- 3fd2f4bc010cdfbc07dd21018dc65bd9370eb7a4 and later · before 9f0e225635475b2285b966271d5e82cba74295b1affected · git
- 3fd2f4bc010cdfbc07dd21018dc65bd9370eb7a4 and later · before 39aaa337449e71a41d4813be0226a722827ba606affected · git
- 6.1.140 and later · before 6.1.153affected · semver
- 6.6.92 and later · before 6.6.107affected · semver
- 6.12.30 and later · before 6.12.48affected · semver
- 6.14.8 and later · before 6.15affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.153-1 | 6.1.153-1 |
| Debian:13 | linux | before 6.12.48-1 | 6.12.48-1 |
| Debian:14 | linux | before 6.16.8-1 | 6.16.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-39868Sep 23, 2025 · erofs: fix runtime warning on truncate_folio_batch_exceptionals()31Monitor
- ← EarlierCVE-2025-39869Sep 23, 2025 · dmaengine: ti: edma: Fix memory allocation size for queue_priority_map28Monitor
- Later →CVE-2025-39871Sep 23, 2025 · dmaengine: idxd: Remove improper idxd_free31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 25e6146c2812487a88f619d5ff6efbdcd5b2bc31 | Vendor (CNA) |
| Linux Linux | 39aaa337449e71a41d4813be0226a722827ba606 | Vendor (CNA) |
| Linux Linux | 6.1.153 | Vendor (CNA) |
| Linux Linux | 6.12.48 | Vendor (CNA) |
| Linux Linux | 6.15 | Vendor (CNA) |
| Linux Linux | 6.6.107 | Vendor (CNA) |
| Linux Linux | 9f0e225635475b2285b966271d5e82cba74295b1 | Vendor (CNA) |
| Linux Linux | df82c7901513fd0fc738052a8e6a330d92cc8ec9 | Vendor (CNA) |
| Linux Linux | ec5430d090d0b6ace8fefa290fc37e88930017d2 | Vendor (CNA) |
| debian:linux | 6.1.153-1 · Debian:12 | Package 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 researchersFinders, 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.
- CVE-2026-31608213 days apartsmb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list()39Monitor
- CVE-2026-31609213 days apartsmb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush()39Monitor
- CVE-2026-43011220 days apartnet/x25: Fix potential double free of skb39Monitor
- CVE-2026-43414227 days apartscsi: qla2xxx: Completely fix fcport double free39Monitor
- CVE-2026-52993274 days aparttipc: fix double-free in tipc_buf_append()39Monitor
- CVE-2026-63888299 days apartscsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()39Monitor
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
- high · data or configuration can be modified
- 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
- High
- Availability impact
- High
Weakness class (CWE)
CWE-415 · Double FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/39aaa337449e71a41d4813be0226a722827ba606
- git.kernel.org/stable/c/9f0e225635475b2285b966271d5e82cba74295b1
- git.kernel.org/stable/c/df82c7901513fd0fc738052a8e6a330d92cc8ec9
- git.kernel.org/stable/c/ec5430d090d0b6ace8fefa290fc37e88930017d2
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.