CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set
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.16% (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 240cd7f2812cc25496b12063d11c823618f364e9, 72f98ef9a4be30d2a60136dd6faee376f780d06c, 7cad37e358970af1bb49030ff01f06a69fa7d985; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.
Low priority for now. Upgrade to Linux Linux 240cd7f2812cc25496b12063d11c823618f364e9, 72f98ef9a4be30d2a60136dd6faee376f780d06c, 7cad37e358970af1bb49030ff01f06a69fa7d985; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 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: iommu: disable SVA when CONFIG_X86 is set Patch series "Fix stale IOTLB entries for kernel address space", v7. This proposes a fix for a security vulnerability related to IOMMU Shared Virtual Addressing (SVA). In an SVA context, an IOMMU can cache kernel page table entries. When a kernel page table page is freed and reallocated for another purpose, the IOMMU might still hold stale, incorrect entries. This can be exploited to cause a use-after-free or write-after-free condition, potentially leading to privilege escalation or data corruption. This solution introduces a deferred freeing mechanism for kernel page table pages, which provides a safe window to notify the IOMMU to invalidate its caches before the page is reused. This patch (of 8): In the IOMMU Shared Virtual Addressing (SVA) context, the IOMMU hardware shares and walks the CPU's page tables. The x86 architecture maps the kernel's virtual address space into the upper portion of every process's page table. Consequently, in an SVA context, the IOMMU hardware can walk and cache kernel page table entries. The Linux kernel currently lacks a notification mechanism for kernel page table changes, specifically when page table pages are freed and reused. The IOMMU driver is only notified of changes to user virtual address mappings. This can cause the IOMMU's internal caches to retain stale entries for kernel VA. Use-After-Free (UAF) and Write-After-Free (WAF) conditions arise when kernel page table pages are freed and later reallocated. The IOMMU could misinterpret the new data as valid page table entries. The IOMMU might then walk into attacker-controlled memory, leading to arbitrary physical memory DMA access or privilege escalation. This is also a Write-After-Free issue, as the IOMMU will potentially continue to write Accessed and Dirty bits to the freed memory while attempting to walk the stale page tables. Currently, SVA contexts are unprivileged and cannot access kernel mappings. However, the IOMMU will still walk kernel-only page tables all the way down to the leaf entries, where it realizes the mapping is for the kernel and errors out. This means the IOMMU still caches these intermediate page table entries, making the described vulnerability a real concern. Disable SVA on x86 architecture until the IOMMU can receive notification to flush the paging cache before freeing the CPU kernel page table pages.
- BDU:2026-08859
- ALSA-2026:21556
- ALSA-2026:39082
- ALSA-2026:39083
- DLA-4499-1
- DSA-6163-1
- RHSA-2026:21556
- RHSA-2026:23237
- RHSA-2026:25218
- RHSA-2026:25533
- RHSA-2026:26462
- RHSA-2026:26515
- RHSA-2026:26535
- RHSA-2026:26563
- RHSA-2026:39082
- RHSA-2026:39083
- RHSA-2026:55445
- RLSA-2026:21556
- SUSE-SU-2026:22673-1
- SUSE-SU-2026:22674-1
- Published
- Jan 13, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/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
- 5.2affected
- 26b25a2b98e45aeb40eedcedc586ad5034cbd984 and later · before 845875f4c6788c88e2334fe5825934821decbdc8affected · git
- 26b25a2b98e45aeb40eedcedc586ad5034cbd984 and later · before b34289505180a83607fcfdce14b5a290d0528476affected · git
- 26b25a2b98e45aeb40eedcedc586ad5034cbd984 and later · before 7cad37e358970af1bb49030ff01f06a69fa7d985affected · git
- 26b25a2b98e45aeb40eedcedc586ad5034cbd984 and later · before 240cd7f2812cc25496b12063d11c823618f364e9affected · git
- 26b25a2b98e45aeb40eedcedc586ad5034cbd984 and later · before c2c3f1a3fd74ef16cf115f0c558616a13a8471b4affected · git
- 26b25a2b98e45aeb40eedcedc586ad5034cbd984 and later · before c341dee80b5df49a936182341b36395c831c2661affected · git
- 26b25a2b98e45aeb40eedcedc586ad5034cbd984 and later · before 72f98ef9a4be30d2a60136dd6faee376f780d06caffected · git
- before 5.2not affected · semver
- 5.10.273 and later · up to and including 5.10.*not affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.2 and later · before 5.15.200
- linux linux kernel5.16 and later · before 6.1.163
- linux linux kernel6.2 and later · before 6.6.120
- linux linux kernel6.7 and later · before 6.12.64
- linux linux kernel6.13 and later · before 6.18.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.143.1.el8_10 | 4.18.0-553.143.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.143.1.rt7.484.el8_10 | 4.18.0-553.143.1.rt7.484.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.143.1.rt7.484.el8_10 | 4.18.0-553.143.1.rt7.484.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.143.1.rt7.484.el8_10 | 4.18.0-553.143.1.rt7.484.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.143.1.rt7.484.el8_10 | 4.18.0-553.143.1.rt7.484.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.143.1.rt7.484.el8_10 | 4.18.0-553.143.1.rt7.484.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.143.1.rt7.484.el8_10 | 4.18.0-553.143.1.rt7.484.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.143.1.rt7.484.el8_10 | 4.18.0-553.143.1.rt7.484.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.143.1.rt7.484.el8_10 | 4.18.0-553.143.1.rt7.484.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.143.1.rt7.484.el8_10 | 4.18.0-553.143.1.rt7.484.el8_10 |
+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-71087Jan 13, 2026 · iavf: fix off-by-one issues in iavf_config_rss_reg()22Monitor
- ← EarlierCVE-2025-71088Jan 13, 2026 · mptcp: fallback earlier on simult connection22Monitor
- Later →CVE-2025-71091Jan 13, 2026 · team: fix check for port enabled in team_queue_override_port_prio_changed()31Monitor
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 | 240cd7f2812cc25496b12063d11c823618f364e9 | Vendor (CNA) |
| Linux Linux | 72f98ef9a4be30d2a60136dd6faee376f780d06c | Vendor (CNA) |
| Linux Linux | 7cad37e358970af1bb49030ff01f06a69fa7d985 | Vendor (CNA) |
| Linux Linux | 845875f4c6788c88e2334fe5825934821decbdc8 | Vendor (CNA) |
| Linux Linux | b34289505180a83607fcfdce14b5a290d0528476 | Vendor (CNA) |
| Linux Linux | c2c3f1a3fd74ef16cf115f0c558616a13a8471b4 | Vendor (CNA) |
| Linux Linux | c341dee80b5df49a936182341b36395c831c2661 | Vendor (CNA) |
| azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 | 6.6.121.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-687.12.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.164-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.164-1~deb11u1 · Debian:11 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+17
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.
- 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-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/72f98ef9a4be30d2a60136dd6faee376f780d06c
- git.kernel.org/stable/c/7cad37e358970af1bb49030ff01f06a69fa7d985
- git.kernel.org/stable/c/845875f4c6788c88e2334fe5825934821decbdc8
- git.kernel.org/stable/c/b34289505180a83607fcfdce14b5a290d0528476
- git.kernel.org/stable/c/c2c3f1a3fd74ef16cf115f0c558616a13a8471b4
- git.kernel.org/stable/c/c341dee80b5df49a936182341b36395c831c2661
Vendor advisories and official records. Exploit/PoC links are deliberately left out.