iommu: disable SVA when CONFIG_X86 is set
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
- 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
- SUSE-SU-2026:22675-1
- SUSE-SU-2026:22676-1
- Published
- Jan 13, 2026
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 5th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
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
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 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.15.200 and later · up to and including 5.15.*not affected · semver
- 6.1.163 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | kernel | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-core | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
| AlmaLinux:9 | kernel-debug-modules-core | before 5.14.0-687.12.1.el9_8 | 5.14.0-687.12.1.el9_8 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
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 | 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) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-687.12.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+16
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/240cd7f2812cc25496b12063d11c823618f364e9
- git.kernel.org/stable/c/72f98ef9a4be30d2a60136dd6faee376f780d06c
- git.kernel.org/stable/c/7cad37e358970af1bb49030ff01f06a69fa7d985
- 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.