CVE-2025-39966: iommufd: Fix race during abort for file descriptors
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.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 17195a7d754a5c6a31888702ca93f6f08f3383ad, 4e034bf045b12852a24d5d33f2451850818ba0c1, e4825368285e33d6360c6c6a6a10d2d83da06e55.
Low priority for now. Upgrade to Linux Linux 17195a7d754a5c6a31888702ca93f6f08f3383ad, 4e034bf045b12852a24d5d33f2451850818ba0c1, e4825368285e33d6360c6c6a6a10d2d83da06e55 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: 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
- Published
- Oct 15, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-362
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- 7.0
- CNA · Linux
- 7.8
- 0.8 point gap
CVSS:3.1/AV:L/AC:L/PR:L/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.
Is your version affected? Check itNoroxi 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 |
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
- 6.11affected
- 07838f7fd529c8a6de44b601d4b7057e6c8d36ed and later · before 17195a7d754a5c6a31888702ca93f6f08f3383adaffected · git
- 07838f7fd529c8a6de44b601d4b7057e6c8d36ed and later · before e4825368285e33d6360c6c6a6a10d2d83da06e55affected · git
- 07838f7fd529c8a6de44b601d4b7057e6c8d36ed and later · before 4e034bf045b12852a24d5d33f2451850818ba0c1affected · git
- before 6.11not affected · semver
- 6.12.50 and later · up to and including 6.12.*not affected · semver
- 6.16.10 and later · up to and including 6.16.*not affected · semver
- 6.17 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.11 and later · before 6.12.50
- linux linux kernel6.13 and later · before 6.16.10
- linux linux kernel6.17
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-124.27.1.el10_1 | 6.12.0-124.27.1.el10_1 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-124.27.1.el10_1 | 6.12.0-124.27.1.el10_1 |
| AlmaLinux:9 | kernel | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-core | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-611.16.1.el9_7 | 5.14.0-611.16.1.el9_7 |
+96
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-39964Oct 13, 2025 · crypto: af_alg - Disallow concurrent writes in af_alg_sendmsgKEV52Plan
- ← EarlierCVE-2025-39965Oct 13, 2025 · xfrm: xfrm_alloc_spi shouldn't use 0 as SPI22Monitor
- Later →CVE-2025-39967Oct 15, 2025 · fbcon: fix integer overflow in fbcon_do_set_font31Monitor
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 | 17195a7d754a5c6a31888702ca93f6f08f3383ad | Vendor (CNA) |
| Linux Linux | 4e034bf045b12852a24d5d33f2451850818ba0c1 | Vendor (CNA) |
| Linux Linux | e4825368285e33d6360c6c6a6a10d2d83da06e55 | Vendor (CNA) |
| almalinux:kernel | 5.14.0-611.16.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-611.16.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-611.16.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-611.16.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-611.16.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-611.16.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-611.16.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-611.16.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-611.16.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-611.16.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-611.16.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-611.16.1.el9_7 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.12.57-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-570.72.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-570.72.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-570.72.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-570.72.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-570.72.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-570.72.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-570.72.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-570.72.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-570.72.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-570.72.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-570.72.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-570.72.1.el9_6 · Red Hat:rhel_eus:9.6::appstream | Package registry (OSV) |
| rocky linux:kernel | 0:5.14.0-611.16.1.el9_7 · Rocky Linux:9 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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.
- Special conditions such as timing or configuration are required.
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
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.