CVE-2025-71202 (GCVE-0-2025-71202)
Vulnerability from cvelistv5
Published
2026-02-14 15:36
Modified
2026-08-05 12:12
Severity ?
8.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Summary
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.
References
Impacted products
Vendor Product Version
Linux Linux Version: 2f26e0a9c9860db290d63e9d85c2c8c09813677f
Version: 2f26e0a9c9860db290d63e9d85c2c8c09813677f
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/Kconfig",
            "drivers/iommu/iommu-sva.c",
            "include/linux/iommu.h",
            "mm/pgtable-generic.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "9f0a7ab700f8620e433b05c57fbd26c92ea186d9",
              "status": "affected",
              "version": "2f26e0a9c9860db290d63e9d85c2c8c09813677f",
              "versionType": "git"
            },
            {
              "lessThan": "e37d5a2d60a338c5917c45296bac65da1382eda5",
              "status": "affected",
              "version": "2f26e0a9c9860db290d63e9d85c2c8c09813677f",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/Kconfig",
            "drivers/iommu/iommu-sva.c",
            "include/linux/iommu.h",
            "mm/pgtable-generic.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.4"
            },
            {
              "lessThan": "4.4",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.19",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.7",
                  "versionStartIncluding": "4.4",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19",
                  "versionStartIncluding": "4.4",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/sva: invalidate stale IOTLB entries for kernel address space\n\nIntroduce a new IOMMU interface to flush IOTLB paging cache entries for\nthe CPU kernel address space.  This interface is invoked from the x86\narchitecture code that manages combined user and kernel page tables,\nspecifically before any kernel page table page is freed and reused.\n\nThis addresses the main issue with vfree() which is a common occurrence\nand can be triggered by unprivileged users.  While this resolves the\nprimary problem, it doesn\u0027t address some extremely rare case related to\nmemory unplug of memory that was present as reserved memory at boot, which\ncannot be triggered by unprivileged users.  The discussion can be found at\nthe link below.\n\nEnable SVA on x86 architecture since the IOMMU can now receive\nnotification to flush the paging cache before freeing the CPU kernel page\ntable pages."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 8.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - An attacker reaches the flaw locally by opening an SVA-enabled userspace accelerator device and submitting PASID-tagged DMA descriptors that force walks of chosen kernel virtual addresses.\nAC:L - On an affected x86 SVA deployment, the attacker controls the device requests and can repeatedly drive unprivileged vfree activity, allocator spraying, and page reuse without relying on an uncontrollable race.\nPR:L - SVA user queues are intended for ordinary processes; after device-node access is granted, the binding and descriptor-submission paths require no capability on hardware marked safe for userspace submission.\nUI:N - The attacker can bind its own address space, prime the IOMMU paging-structure cache, and trigger reclamation and reuse without another user\u0027s involvement.\nS:C - The flaw bypasses the PASID/IOMMU DMA isolation boundary, allowing a process-scoped SVA context to access host physical memory outside its security authority.\nC:H - A reused page-table page can contain attacker-controlled entries that the IOMMU interprets as translations, enabling arbitrary physical-memory DMA reads of kernel or other-process data.\nI:H - The forged translation path can enable arbitrary physical-memory DMA writes and privilege escalation; page walks can also write Accessed and Dirty bits into freed memory.\nA:H - Arbitrary physical-memory DMA writes and page-table write-after-free can corrupt critical kernel state, causing a kernel crash, panic, or system hang."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:12:31.577Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/9f0a7ab700f8620e433b05c57fbd26c92ea186d9"
        },
        {
          "url": "https://git.kernel.org/stable/c/e37d5a2d60a338c5917c45296bac65da1382eda5"
        }
      ],
      "title": "iommu/sva: invalidate stale IOTLB entries for kernel address space",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-71202",
    "datePublished": "2026-02-14T15:36:06.588Z",
    "dateReserved": "2026-01-31T11:36:51.194Z",
    "dateUpdated": "2026-08-05T12:12:31.577Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.