« Volver al listado

CVE-2026-90242

Estado: RecibidaSin puntuar—

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.

Leer descripción completaMostrar menos

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.

CVSS

NVD no ha asignado puntuación CVSS a esta CVE (habitual desde el cambio de política de abril de 2026).

Probabilidad de explotación (EPSS)

EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).

Tecnologías afectadas (1)

⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.

Linux — Linux KernelAI

Referencias

JSON original (NVD)

Mostrar
{
  "id": "CVE-2026-90242",
  "cveTags": [],
  "metrics": {},
  "affected": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "affectedData": [
        {
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "product": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "17fce9d2336d952b95474248303e5e7d9777f2e0",
              "lessThan": "143cd37ce76527ddd6f6dbac4a89bde31fb8b0dc",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "17fce9d2336d952b95474248303e5e7d9777f2e0",
              "lessThan": "236dd58fabd2e951b940a6ad88b81147899ed311",
              "versionType": "git"
            }
          ],
          "programFiles": [
            "drivers/iommu/intel/iommu.c"
          ],
          "defaultStatus": "unaffected"
        },
        {
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "product": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.16"
            },
            {
              "status": "unaffected",
              "version": "0",
              "lessThan": "6.16",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "7.2.6",
              "versionType": "semver",
              "lessThanOrEqual": "7.2.*"
            },
            {
              "status": "unaffected",
              "version": "7.3-rc1",
              "versionType": "original_commit_for_fix",
              "lessThanOrEqual": "*"
            }
          ],
          "programFiles": [
            "drivers/iommu/intel/iommu.c"
          ],
          "defaultStatus": "affected"
        }
      ]
    }
  ],
  "published": "2026-09-17T17:17:20.190",
  "references": [
    {
      "url": "https://git.kernel.org/stable/c/143cd37ce76527ddd6f6dbac4a89bde31fb8b0dc",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    },
    {
      "url": "https://git.kernel.org/stable/c/236dd58fabd2e951b940a6ad88b81147899ed311",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "vulnStatus": "Received",
  "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->iopf_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->iopf_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."
    }
  ],
  "lastModified": "2026-09-17T17:17:20.190",
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}