CVE-2025-71089

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-01-13. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

January 13, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Aug 3, 2026
No patch confirmed yet.
generic

iommu: disable SVA when CONFIG_X86 is set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c341dee80b5df49a936182341b36395c831c2661
generic

iommu: disable SVA when CONFIG_X86 is set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c2c3f1a3fd74ef16cf115f0c558616a13a8471b4
generic

iommu: disable SVA when CONFIG_X86 is set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b34289505180a83607fcfdce14b5a290d0528476
generic

iommu: disable SVA when CONFIG_X86 is set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7cad37e358970af1bb49030ff01f06a69fa7d985
generic

iommu: disable SVA when CONFIG_X86 is set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72f98ef9a4be30d2a60136dd6faee376f780d06c
generic

iommu: disable SVA when CONFIG_X86 is set - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/240cd7f2812cc25496b12063d11c823618f364e9

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-553.143.1.el8_102026-07-14redhat
redhatkernel-rt-0:4.18.0-553.143.1.rt7.484.el8_102026-07-14redhat
redhatkernel-rt-0:5.14.0-284.176.1.rt14.461.el9_22026-06-17redhat
redhatkernel-0:4.18.0-305.194.1.el8_42026-06-17redhat
redhatkernel-0:4.18.0-477.147.1.el8_82026-06-17redhat
redhatkernel-0:5.14.0-284.176.1.el9_22026-06-17redhat
redhatkernel-0:4.18.0-372.195.1.el8_62026-06-12redhat
redhatkernel-0:5.14.0-570.120.1.el9_62026-06-11redhat
redhatkernel-0:5.14.0-427.129.1.el9_42026-06-04redhat
redhatkernel-0:5.14.0-687.12.1.el9_82026-05-28redhat
ubuntulinux-tools-gcp-edge (6.8.0-1054.57~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1020.20) @ noble2026-05-21ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1014.14) @ questing2026-05-21ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1051.54) @ noble2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-22.22) @ questing2026-05-21ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1054.60) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1054.60+fips1) @ noble2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-05-21ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1011.11) @ questing2026-05-21ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1022.22) @ noble2026-05-21ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1010.11~24.04.1) @ noble2026-05-21ubuntu
ubuntulinux-virtual-6.8 (6.8.0-110.110) @ noble2026-05-21ubuntu
ubuntulinux-tools-gcp-edge (6.17.0-1012.12~24.04.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1051.54.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1054.57+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1052.56) @ noble2026-05-21ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1047.48) @ noble2026-05-21ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2042.43) @ noble2026-05-21ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1049.50) @ noble2026-05-21ubuntu
linuxKernel @ 5.15.200osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
linux-6.16.1.106-3~deb11u1 ... 6.1.162-1~deb11u1 (15 versions)6.1.164-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (47 versions)6.1.164-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)6.12.69-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (92 versions)6.18.5-1

Additional Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 4× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 170 total refreshes for this CVE.

  1. 2026-09-07 16:00 UTCEPSS rescore
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-02 14:11 UTCEPSS rescore
  5. 2026-09-01 13:53 UTCEPSS rescore
  6. 2026-08-31 08:25 UTCOSV refresh
  7. 2026-08-30 01:21 UTCEPSS rescore
  8. 2026-08-28 21:40 UTCEPSS rescore
  9. 2026-08-27 14:24 UTCEPSS rescore
  10. 2026-08-26 14:45 UTCEPSS rescore
  11. 2026-08-25 13:48 UTCEPSS rescore
  12. 2026-08-24 14:16 UTCEPSS rescore
  13. 2026-08-23 00:18 UTCEPSS rescore
  14. 2026-08-21 23:48 UTCEPSS rescore
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-19 17:03 UTCEPSS rescore
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 13:46 UTCEPSS rescore
  19. 2026-08-16 14:55 UTCEPSS rescore
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 14:40 UTCEG score recompute
  23. 2026-08-14 14:40 UTCVendor advisory
  24. 2026-08-14 14:40 UTCGHSA enrichment
  25. 2026-08-13 22:00 UTCEPSS rescore
Show 75 more
  1. 2026-08-12 13:50 UTCEPSS rescore
  2. 2026-08-11 13:42 UTCEPSS rescore
  3. 2026-08-10 23:59 UTCEPSS rescore
  4. 2026-08-09 20:11 UTCEG score recompute
  5. 2026-08-09 20:11 UTCVendor advisory
  6. 2026-08-09 20:11 UTCGHSA enrichment
  7. 2026-08-09 13:46 UTCEPSS rescore
  8. 2026-08-08 16:36 UTCEPSS rescore
  9. 2026-08-08 00:54 UTCEG score recompute
  10. 2026-08-08 00:54 UTCVendor advisory
  11. 2026-08-08 00:54 UTCGHSA enrichment
  12. 2026-08-06 13:46 UTCEPSS rescore
  13. 2026-08-06 05:55 UTCEG score recompute
  14. 2026-08-06 05:55 UTCVendor advisory
  15. 2026-08-06 05:55 UTCGHSA enrichment
  16. 2026-08-05 19:17 UTCEPSS rescore
  17. 2026-08-05 12:46 UTCEG score recompute
  18. 2026-08-05 12:46 UTCVendor advisory
  19. 2026-08-05 12:46 UTCGHSA enrichment
  20. 2026-08-04 10:37 UTCEPSS rescore
  21. 2026-08-03 10:35 UTCEPSS rescore
  22. 2026-08-02 23:52 UTCEG score recompute
  23. 2026-08-02 23:52 UTCVendor advisory
  24. 2026-08-02 23:52 UTCGHSA enrichment
  25. 2026-08-02 02:26 UTCEPSS rescore
  26. 2026-08-01 04:15 UTCEPSS rescore
  27. 2026-07-30 16:27 UTCEPSS rescore
  28. 2026-07-30 01:30 UTCEPSS rescore
  29. 2026-07-27 14:13 UTCEPSS rescore
  30. 2026-07-27 02:09 UTCOSV refresh
  31. 2026-07-26 14:54 UTCEPSS rescore
  32. 2026-07-26 14:54 UTCEPSS rescore
  33. 2026-07-24 14:17 UTCEPSS rescore
  34. 2026-07-23 14:18 UTCEPSS rescore
  35. 2026-07-23 14:18 UTCEPSS rescore
  36. 2026-07-23 03:03 UTCEG score recompute
  37. 2026-07-22 14:08 UTCEPSS rescore
  38. 2026-07-21 15:24 UTCEPSS rescore
  39. 2026-07-20 17:08 UTCEPSS rescore
  40. 2026-07-19 14:30 UTCEPSS rescore
  41. 2026-07-19 14:30 UTCEPSS rescore
  42. 2026-07-19 02:28 UTCEPSS rescore
  43. 2026-07-19 02:28 UTCEPSS rescore
  44. 2026-07-18 10:04 UTCEPSS rescore
  45. 2026-07-18 10:04 UTCEPSS rescore
  46. 2026-07-16 17:02 UTCEPSS rescore
  47. 2026-07-16 17:02 UTCEPSS rescore
  48. 2026-07-15 16:57 UTCEPSS rescore
  49. 2026-07-15 16:57 UTCEPSS rescore
  50. 2026-07-15 02:00 UTCEPSS rescore
  51. 2026-07-15 01:59 UTCEPSS rescore
  52. 2026-07-13 06:12 UTCEPSS rescore
  53. 2026-07-12 05:46 UTCEPSS rescore
  54. 2026-07-12 05:46 UTCEPSS rescore
  55. 2026-07-11 08:27 UTCEPSS rescore
  56. 2026-07-11 08:27 UTCEPSS rescore
  57. 2026-07-09 20:45 UTCOSV refresh
  58. 2026-07-09 19:10 UTCEPSS rescore
  59. 2026-07-08 15:15 UTCEPSS rescore
  60. 2026-07-07 13:46 UTCEPSS rescore
  61. 2026-07-06 02:23 UTCEPSS rescore
  62. 2026-07-05 02:30 UTCEPSS rescore
  63. 2026-07-05 02:30 UTCEPSS rescore
  64. 2026-07-04 06:31 UTCEPSS rescore
  65. 2026-07-04 06:31 UTCEPSS rescore
  66. 2026-07-01 15:06 UTCEPSS rescore
  67. 2026-06-30 23:22 UTCEPSS rescore
  68. 2026-06-30 23:22 UTCEPSS rescore
  69. 2026-06-29 14:06 UTCEPSS rescore
  70. 2026-06-29 14:06 UTCEPSS rescore
  71. 2026-06-28 14:07 UTCEPSS rescore
  72. 2026-06-28 14:07 UTCEPSS rescore
  73. 2026-06-28 04:56 UTCEPSS rescore
  74. 2026-06-28 04:56 UTCEPSS rescore
  75. 2026-06-27 03:08 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-71089?
CVE-2025-71089 is a high vulnerability published on January 13, 2026. 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…
When was CVE-2025-71089 disclosed?
CVE-2025-71089 was first published in the National Vulnerability Database on January 13, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71089 actively exploited?
CVE-2025-71089 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.2% of all scored CVEs.
What is the CVSS score of CVE-2025-71089?
CVE-2025-71089 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-71089?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71089, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71089

Explore →

Is Your Infrastructure Affected by CVE-2025-71089?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.