LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71202: iommu/sva: invalidate stale IOTLB entries for kernel address space

In the Linux kernel, the following vulnerability has been resolved: iommu/sva: invalidate stale IOTLB entries for kernel address space Introduce a new IOMMU interface to flush IOTLB paging cache entries for the CPU kernel address space. This interface is invoked from the x86 architecture code that manages combined user and kernel page tables, specifically before any kernel page table page is freed and reused. This addresses the main issue with vfree() which is a common occurrence and can be triggered by unprivileged users. While this resolves the primary problem, it doesn't address some extremely rare case related to memory unplug of memory that was present as reserved memory at boot, which cannot be triggered by unprivileged users. The discussion can be found at the link below. Enable SVA on x86 architecture since the IOMMU can now receive notification to flush the paging cache before freeing the CPU kernel page table pages.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue concerns stale IOMMU translation cache entries for kernel memory. Under some conditions, kernel page-table pages could be freed and reused before the IOMMU was told to drop old entries. The source notes common vfree() activity can be triggered by unprivileged users, but gives no CVSS, impact class, or exploitation evidence.

Executive priority

Treat this as a kernel-maintenance priority, not a confirmed emergency. Patch affected Linux systems through normal expedited kernel update channels, especially infrastructure where kernel isolation failures would have high business impact.

Technical view

The fix adds an IOMMU interface to flush IOTLB paging-cache entries for the CPU kernel address space before x86 kernel page-table pages are freed and reused. It addresses the primary vfree() path and leaves only an extremely rare memory-unplug case that sources say is not unprivileged-triggerable.

Likely exposure

Exposure is limited to Linux kernels containing the affected upstream code path, especially x86 systems using IOMMU/SVA behavior. The source lists Linux as affected and references stable kernel commits, but distribution backport status is not provided.

Exploitation context

The source says unprivileged users can trigger the common vfree() condition involved in the primary problem. It does not state successful exploitation, public exploit availability, attacker impact, or CISA KEV listing.

Researcher notes

Evidence is incomplete: no CVSS, CWE, exploitation report, or detailed impact is provided. The main source-grounded risk signal is unprivileged triggerability of the vfree() path plus stale IOTLB entries before page-table reuse.

Mitigation direction

  • Review vendor kernel advisories for CVE-2025-71202 and affected distribution packages.
  • Prioritize kernel updates that include the referenced stable commits.
  • Track systems using x86 IOMMU/SVA-capable configurations for earlier remediation.
  • Avoid inventing local mitigations; use vendor guidance where patch timing differs.

Validation and detection

  • Inventory Linux kernel versions and distribution package revisions across affected assets.
  • Check whether installed kernels include the referenced upstream stable fixes.
  • Confirm vendor advisories map CVE-2025-71202 to your deployed packages.
  • Retest kernel-dependent workloads after patching, especially virtualization or device-assignment use cases.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-71202 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2f26e0a9c9860db290d63e9d85c2c8c09813677f, 2f26e0a9c9860db290d63e9d85c2c8c09813677funaffected
LinuxLinux4.4, 0, 6.18.7, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.