{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2026-09-08T17:08:26.757Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "http://xenbits.xen.org/xsa/advisory-509.html"
          },
          {
            "url": "http://www.openwall.com/lists/oss-security/2026/09/08/6"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unknown",
          "product": "Xen",
          "vendor": "Xen",
          "versions": [
            {
              "status": "unknown",
              "version": "consult Xen advisory XSA-509"
            }
          ]
        }
      ],
      "configurations": [
        {
          "lang": "en",
          "value": "All Xen versions from at least 3.2 onwards are affected.  Older versions\nhave not been inspected.\n\nOnly HVM guests with assigned PCI devices can leverage the vulnerability."
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "This issue was discovered by Jan Beulich of SUSE."
        }
      ],
      "datePublic": "2026-09-08T12:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "When guests are terminated, various pieces of cleanup need carrying out.\nThe cleaning up of PCI devices which were assigned to guests, and the\nassociated removal of tracking structures for IRQs used by the devices\noccurs relatively early in the process.  Unfortunately after that point\nthe guest about to be terminated could cause its device model (DM) to\nre-establish such tracking structures, by having it bind one or more IRQs\nanew.  While some of those tracking structures would still be cleaned up\nlater on, at least one would not be."
        }
      ],
      "impacts": [
        {
          "descriptions": [
            {
              "lang": "en",
              "value": "A HVM guest with one or more PCI devices assigned can cause a memory leak\nin the hypervisor, possibly leading to Denial of Service (DoS) of the\nentire host."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-08T12:10:52.643Z",
        "orgId": "23aa2041-22e1-471f-9209-9b7396fa234f",
        "shortName": "XEN"
      },
      "references": [
        {
          "url": "https://xenbits.xenproject.org/xsa/advisory-509.html"
        }
      ],
      "title": "x86: DMs may cause mem leak by IRQ binding",
      "workarounds": [
        {
          "lang": "en",
          "value": "Running only PV or PVH guests will avoid the vulnerability.\n\nRunning only HVM guests without passing through PCI devices to them will\nalso avoid the vulnerability."
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "23aa2041-22e1-471f-9209-9b7396fa234f",
    "assignerShortName": "XEN",
    "cveId": "CVE-2026-62437",
    "datePublished": "2026-09-08T12:10:52.643Z",
    "dateReserved": "2026-07-14T10:28:12.655Z",
    "dateUpdated": "2026-09-08T17:08:26.757Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-62437\",\"sourceIdentifier\":\"security@xen.org\",\"published\":\"2026-09-08T13:17:19.623\",\"lastModified\":\"2026-09-08T19:20:25.117\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"When guests are terminated, various pieces of cleanup need carrying out.\\nThe cleaning up of PCI devices which were assigned to guests, and the\\nassociated removal of tracking structures for IRQs used by the devices\\noccurs relatively early in the process.  Unfortunately after that point\\nthe guest about to be terminated could cause its device model (DM) to\\nre-establish such tracking structures, by having it bind one or more IRQs\\nanew.  While some of those tracking structures would still be cleaned up\\nlater on, at least one would not be.\"}],\"affected\":[{\"source\":\"security@xen.org\",\"affectedData\":[{\"vendor\":\"Xen\",\"product\":\"Xen\",\"defaultStatus\":\"unknown\",\"versions\":[{\"version\":\"consult Xen advisory XSA-509\",\"status\":\"unknown\"}]}]}],\"metrics\":{},\"references\":[{\"url\":\"https://xenbits.xenproject.org/xsa/advisory-509.html\",\"source\":\"security@xen.org\"},{\"url\":\"http://www.openwall.com/lists/oss-security/2026/09/08/6\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"http://xenbits.xen.org/xsa/advisory-509.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
    "redhat_vex": {
      "current_release_date": "2026-09-08T21:26:22+00:00",
      "cve": "CVE-2026-62437",
      "id": "CVE-2026-62437",
      "initial_release_date": "2026-09-08T12:10:52.643000+00:00",
      "product_status:known_not_affected": "1",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "xen: Xen: Memory leak due to re-established IRQ tracking structures during guest termination",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-62437.json",
      "version": "3"
    }
  }
}