cve.bz

CVE-2025-39966 linux linux kernel: Race Condition

7.0 highEPSS 0.1%Fix available

High (7.0) in linux linux kernel. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: iommufd: Fix race during abort for file descriptors fput() doesn't actually call file_operations release() synchronously, it puts the file on a work queue and it will be released eventually. This is normally fine, except for iommufd the file and the iommufd_object are tied to gether. The file has the object as it's private_data and holds a users refcount, while the object is expected to remain alive as long as the file is. When the allocation of a new object aborts before installing the file it will fput() the file and then go on to immediately kfree() the obj. This causes a UAF once the workqueue completes the fput() and tries to decrement the users refcount. Fix this by putting the core code in charge of the file lifetime, and call __fput_sync() during abort to ensure that release() is called before kfree. __fput_sync() is a bit too tricky to open code in all the object implementations. Instead the objects tell the core code where the file pointer is and the core will take care of the life cycle. If the object is successfully allocated then the file will hold a users refcount and the iommufd_object cannot be destroyed. It is worth noting that close(); ioctl(IOMMU_DESTROY); doesn't have an issue because close() is already using a synchronous version of fput(). The UAF looks like this: BUG: KASAN: slab-use-after-free in iommufd_eventq_fops_release+0x45/0xc0 drivers/iommu/iommufd/eventq.c:376 Write of size 4 at addr ffff888059c97804 by task syz.0.46/6164 CPU: 0 UID: 0 PID: 6164 Comm: syz.0.46 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcd/0x630 mm/kasan/report.c:482 kasan_report+0xe0/0x110 mm/kasan/report.c:595 check_region_inline mm/kasan/generic.c:183 [inline] kasan_check_range+0x100/0x1b0 mm/kasan/generic.c:189 instrument_atomic_read_write include/linux/instrumented.h:96 [inline] atomic_fetch_sub_release include/linux/atomic/atomic-instrumented.h:400 [inline] __refcount_dec include/linux/refcount.h:455 [inline] refcount_dec include/linux/refcount.h:476 [inline] iommufd_eventq_fops_release+0x45/0xc0 drivers/iommu/iommufd/eventq.c:376 __fput+0x402/0xb70 fs/file_table.c:468 task_work_run+0x14d/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xeb/0x110 kernel/entry/common.c:43 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline] do_syscall_64+0x41c/0x4c0 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Severity

CVSS 3.1

7.0 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-39966 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-39966?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-39966?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-39966 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.11 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.50
Linux6.166.16.10
Linuxlater releases6.17

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13linux6.12.57-1DEBIAN-CVE-2025-39966
Debian14linux6.16.10-1DEBIAN-CVE-2025-39966
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-39966
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-39966
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-39966
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2025-39966
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 16 moreno fix listedUBUNTU-CVE-2025-39966
Ubuntu25.10linux6.17.0-6.6UBUNTU-CVE-2025-39966
Ubuntu25.10linux-aws, linux-gcp, linux-oracle6.17.0-1003.3UBUNTU-CVE-2025-39966
Ubuntu25.10linux-azure6.17.0-1006.6UBUNTU-CVE-2025-39966
Ubuntu25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-39966
Ubuntu25.10linux-raspi6.17.0-1004.4UBUNTU-CVE-2025-39966
Ubuntu25.10linux-realtime6.17.0-1002.3UBUNTU-CVE-2025-39966
Ubuntu25.10linux-riscv6.17.0-6.6.1UBUNTU-CVE-2025-39966
1 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 29 more0:5.14.0-611.16.1.el9_7RHSA-2025:23241
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 45 more0:5.14.0-611.16.1.el9_7RHSA-2025:23241
Red Hatenterprise_linux:9::crblibperf, perf-debuginfo, kernel-debuginfo and 16 more0:5.14.0-611.16.1.el9_7RHSA-2025:23241
Red Hatenterprise_linux:9::nfvkernel-rt, kernel-rt-core, perf-debuginfo and 18 more0:5.14.0-611.16.1.el9_7RHSA-2025:23241
Red Hatenterprise_linux:9::realtimekernel-rt, kernel-rt-64k, kernel-rt-core and 35 more0:5.14.0-611.16.1.el9_7RHSA-2025:23241
Red Hatenterprise_linux:10.1rv, perf, rtla and 87 more0:6.12.0-124.27.1.el10_1RHSA-2026:0453
Red Hatenterprise_linux_eus:10.0rv, perf, rtla and 88 more0:6.12.0-55.50.1.el10_0RHSA-2025:23250
Red Hatrhel_eus:9.6::appstreamrv, perf, rtla and 29 more0:5.14.0-570.72.1.el9_6RHSA-2025:22802
Red Hatrhel_eus:9.6::baseoskernel, kernel-64k, kernel-core and 45 more0:5.14.0-570.72.1.el9_6RHSA-2025:22802
Red Hatrhel_eus:9.6::crblibperf, perf-debuginfo, kernel-debuginfo and 16 more0:5.14.0-570.72.1.el9_6RHSA-2025:22802
Red Hatrhel_eus:9.6::nfvkernel-rt, kernel-rt-kvm, kernel-rt-core and 20 more0:5.14.0-570.72.1.el9_6RHSA-2025:22802
Red Hatrhel_eus:9.6::realtimekernel-rt, kernel-rt-64k, kernel-rt-core and 35 more0:5.14.0-570.72.1.el9_6RHSA-2025:22802
AlmaLinux9rv, perf, rtla and 71 more5.14.0-611.16.1.el9_7ALSA-2025:23241
AlmaLinux10kernel-doc, kernel-abi-stablelists6.12.0-124.27.1.el10_1ALSA-2026:0453
Rocky Linux9kernel0:5.14.0-611.16.1.el9_7RLSA-2025:23241
Rocky Linux10kernel0:6.12.0-124.27.1.el10_1RLSA-2026:0453
Alpaquita25linux-lts6.12.51-r0BELL-CVE-2025-39966
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-39966

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat rates this vulnerability as Moderate because exploitation requires local access and relies on winning a race condition during failed IOMMU object allocations. While a successful exploit could trigger memory corruption leading to system instability or potential privilege escalation, access to the iommufd interface is typically limited to administrative users or virtualization services. Typical Red Hat Enterprise Linux environments that do not grant unprivileged access to device passthrough features remain protected against low-privileged exploitation.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernel-0:6.12.0-124.27.1.el10_1Fixed 2026-01-12RHSA-2026:0453
Red Hat Enterprise Linux 10.0 Extended Update Supportkernel-0:6.12.0-55.50.1.el10_0Fixed 2025-12-17RHSA-2025:23250
Red Hat Enterprise Linux 9kernel-0:5.14.0-611.16.1.el9_7Fixed 2025-12-17RHSA-2025:23241
Red Hat Enterprise Linux 9.6 Extended Update Supportkernel-0:5.14.0-570.72.1.el9_6Fixed 2025-12-09RHSA-2025:22802
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernel-rtAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-39966.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON