CVE-2026-90242 (GCVE-0-2026-90242)
Vulnerability from cvelistv5
Published
2026-09-17 16:07
Modified
2026-10-19 09:00
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix iopf_refcount leak on RID domain replacement intel_iommu_attach_device() enables IOPF for the new domain but never disables it for the old one. device_block_translation(), called at the start of the function, tears down translation but does not touch any IOPF state; blocking_domain_attach_dev() has to call iopf_for_domain_remove() explicitly before invoking it for exactly this reason. identity_domain_attach_dev() has the same problem. Its comment claims that no PRI handling is needed because the device has been put in the blocking state, but the blocking state and the IOPF reference count are independent of each other. As a result, replacing a domain that has an iopf_handler with another domain at RID level leaks a reference in info->iopf_refcount. The count never drops back to zero, so iopf_queue_remove_device() is never called and iommu_disable_pci_pri() triggers its WARN_ON(info->iopf_refcount) when the device is released. The PASID paths already handle this correctly by way of iopf_for_domain_replace(); convert the two RID paths to do the same. Using the replace helper rather than a bare remove keeps the enable before the disable, so the reference count does not transiently reach zero and evict the device from the IOPF queue.
References
Impacted products
Vendor Product Version
Linux Linux Version: 17fce9d2336d952b95474248303e5e7d9777f2e0
Version: 17fce9d2336d952b95474248303e5e7d9777f2e0
Version: 17fce9d2336d952b95474248303e5e7d9777f2e0
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/iommu/intel/iommu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "243bf1e45e40be4705aae17c5044bf83df5f4a92",
              "status": "affected",
              "version": "17fce9d2336d952b95474248303e5e7d9777f2e0",
              "versionType": "git"
            },
            {
              "lessThan": "143cd37ce76527ddd6f6dbac4a89bde31fb8b0dc",
              "status": "affected",
              "version": "17fce9d2336d952b95474248303e5e7d9777f2e0",
              "versionType": "git"
            },
            {
              "lessThan": "236dd58fabd2e951b940a6ad88b81147899ed311",
              "status": "affected",
              "version": "17fce9d2336d952b95474248303e5e7d9777f2e0",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/iommu/intel/iommu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.16"
            },
            {
              "lessThan": "6.16",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.57",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.57",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.6",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/vt-d: Fix iopf_refcount leak on RID domain replacement\n\nintel_iommu_attach_device() enables IOPF for the new domain but never\ndisables it for the old one.  device_block_translation(), called at the\nstart of the function, tears down translation but does not touch any IOPF\nstate; blocking_domain_attach_dev() has to call iopf_for_domain_remove()\nexplicitly before invoking it for exactly this reason.\n\nidentity_domain_attach_dev() has the same problem.  Its comment claims\nthat no PRI handling is needed because the device has been put in the\nblocking state, but the blocking state and the IOPF reference count are\nindependent of each other.\n\nAs a result, replacing a domain that has an iopf_handler with another\ndomain at RID level leaks a reference in info-\u003eiopf_refcount.  The count\nnever drops back to zero, so iopf_queue_remove_device() is never called\nand iommu_disable_pci_pri() triggers its WARN_ON(info-\u003eiopf_refcount)\nwhen the device is released.\n\nThe PASID paths already handle this correctly by way of\niopf_for_domain_replace(); convert the two RID paths to do the same.\nUsing the replace helper rather than a bare remove keeps the enable\nbefore the disable, so the reference count does not transiently reach\nzero and evict the device from the IOPF queue."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T09:00:18.248Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/243bf1e45e40be4705aae17c5044bf83df5f4a92"
        },
        {
          "url": "https://git.kernel.org/stable/c/143cd37ce76527ddd6f6dbac4a89bde31fb8b0dc"
        },
        {
          "url": "https://git.kernel.org/stable/c/236dd58fabd2e951b940a6ad88b81147899ed311"
        }
      ],
      "title": "iommu/vt-d: Fix iopf_refcount leak on RID domain replacement",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-90242",
    "datePublished": "2026-09-17T16:07:45.817Z",
    "dateReserved": "2026-09-11T19:38:34.795Z",
    "dateUpdated": "2026-10-19T09:00:18.248Z",
    "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.