CVE-2025-39871

dmaengine: idxd: Remove improper idxd_free

HIGH
7.8
CVSS Score
Published: September 23, 2025 at 06:00 AM UTC
Updated: October 19, 2026 at 09:10 PM UTC
4 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSiplus S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Remove improper idxd_free The call to idxd_free() introduces a duplicate put_device() leading to a reference count underflow: refcount_t: underflow; use-after-free. WARNING: CPU: 15 PID: 4428 at lib/refcount.c:28 refcount_warn_saturate+0xbe/0x110 ... Call Trace: <TASK> idxd_remove+0xe4/0x120 [idxd] pci_device_remove+0x3f/0xb0 device_release_driver_internal+0x197/0x200 driver_detach+0x48/0x90 bus_remove_driver+0x74/0xf0 pci_unregister_driver+0x2e/0xb0 idxd_exit_module+0x34/0x7a0 [idxd] __do_sys_delete_module.constprop.0+0x183/0x280 do_syscall_64+0x54/0xd70 entry_SYSCALL_64_after_hwframe+0x76/0x7e The idxd_unregister_devices() which is invoked at the very beginning of idxd_remove(), already takes care of the necessary put_device() through the following call path: idxd_unregister_devices() -> device_unregister() -> put_device() In addition, when CONFIG_DEBUG_KOBJECT_RELEASE is enabled, put_device() may trigger asynchronous cleanup via schedule_delayed_work(). If idxd_free() is called immediately after, it can result in a use-after-free. Remove the improper idxd_free() to avoid both the refcount underflow and potential memory corruption during module unload.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.1.140 ≤ v < 6.26.12.30 ≤ v < 6.12.486.14.8 ≤ v < 6.156.15.1 ≤ v < 6.16.86.6.92 ≤ v < 6.6.10721f9f5cd9a0c75084d4369ba0b8c4f695c41dea72b7a961cea0e5b65afda911f76d14fec5c98d0246.1.1406.12.306.14.86.156.15 rc76.176.17 rc16.17 rc26.17 rc36.17 rc46.17 rc56.6.9268ac5a01f635b3791196fd1c39bc48497252c36fd2d05fd0fc95c4defed6f7b87550e20e8baa1d97d5449ff1b04dfe9ed8e455769aa01e4c2ccf6805
Vendor states this is fixed in 0e95ee7f532b21206fe3f1c4054002b0d21e3b9c (fixed)
Vendor states this is fixed in 24414bbcb37e1af95190af36c21ae51d497e1a9e (fixed)
Vendor states this is fixed in da4fbc1488a4cec6748da685181ee4449a878dac (fixed)
Vendor states this is fixed in dd7a7e43269711d757fc260b0bbdf7138f75de11 (fixed)
Vendor states this is fixed in f41c538881eec4dcf5961a242097d447f848cda6 (fixed)
Vendor states this is fixed in 6.1.160 (unaffected)
Vendor states this is fixed in 6.12.48 (unaffected)
Vendor states this is fixed in 6.15 (unaffected)
Vendor states this is fixed in 6.16.8 (unaffected)
Vendor states this is fixed in 6.17 (unaffected)
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.107 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card