CVE-2025-39871

Advisory lineage Upstream: 0 Downstream: 30
Modified
Published: 23 Sept 2025, 06:00
Last modified:23 May 2026, 16:00

Vulnerability Summary

Overall Risk (default)
medium
31/100
CVSS Score
7.8 HIGH
v3.1 (nvd)
EPSS Score
0.02% LOW
0% probability 0.00%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

23 Sept 2025, 06:00
Published
Vulnerability first disclosed
23 May 2026, 16:00
Last Modified
Vulnerability information updated

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.

CVSS Metrics

  • v3.1•HIGH•Score: 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 0.02%• Percentile: 6%

Techniques & Countermeasures

  • CWE-416•Use After Free

    The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Affected Systems

  • linux•linux

    ≥ 68ac5a01f635b3791196fd1c39bc48497252c36f, < 24414bbcb37e1af95190af36c21ae51d497e1a9e | ≥ d2d05fd0fc95c4defed6f7b87550e20e8baa1d97, < 0e95ee7f532b21206fe3f1c4054002b0d21e3b9c | ≥ 21f9f5cd9a0c75084d4369ba0b8c4f695c41dea7, < dd7a7e43269711d757fc260b0bbdf7138f75de11 | ≥ d5449ff1b04dfe9ed8e455769aa01e4c2ccf6805, < da4fbc1488a4cec6748da685181ee4449a878dac | ≥ d5449ff1b04dfe9ed8e455769aa01e4c2ccf6805, < f41c538881eec4dcf5961a242097d447f848cda6 | 2b7a961cea0e5b65afda911f76d14fec5c98d024 | ≥ 6.1.140, < 6.1.160 | ≥ 6.6.92, < 6.6.107 | ≥ 6.12.30, < 6.12.48 | ≥ 6.14.8, < 6.15 | 6.15

  • linux•linux_kernel

    ≥ 6.1.140, < 6.2 | ≥ 6.6.92, < 6.6.107 | ≥ 6.12.30, < 6.12.48 | ≥ 6.14.8, < 6.15 | ≥ 6.15.1, < 6.16.8 | 6.15 | 6.15:rc7 | 6.17:rc1 | 6.17:rc2 | 6.17:rc3 | 6.17:rc4 | 6.17:rc5

References (5)