{
  "affected": [
    {
      "ranges": [
        {
          "events": [
            {
              "introduced": "6f38f8c574642a822f2e85f079fa29a49176c49c"
            },
            {
              "fixed": "6aef7cf800098749ff5d660222efaf6e01e98c09"
            },
            {
              "fixed": "9784e5ca91b37b387f3f414af4340c54f7a63566"
            },
            {
              "fixed": "12c1f6e03f944e399bd2c88441dca5dc702b95a5"
            }
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "type": "GIT"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Linux",
        "name": "Kernel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "6.17.0"
            },
            {
              "fixed": "6.18.55"
            }
          ],
          "type": "ECOSYSTEM"
        },
        {
          "events": [
            {
              "introduced": "6.19.0"
            },
            {
              "fixed": "7.2.9"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98472.json"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV\n\nUnconditionally free SEV's \"have run CPUs\" cpumask in the VM destroy path,\ni.e. even for what appear to be non-SEV VMs, as an SEV VM becomes a non-SEV\nVM if its state is intra-host migrated.  Alternatively, the mask could be\nfreed in sev_migrate_from() when \"converting\" the source VM, but that gets\nannoying because ideally KVM would nullify the mask to guard against UAF,\nand nullifying the mask would need be conditioned on CPUMASK_OFFSTACK=y.\n\nFreeing the mask during sev_migrate_from() is also not robust against other\nKVM bugs, though that's kind of a moot point since any such bugs would show\nup even if sev-\u003eactive is never set.  I.e. KVM must get that side of things\ncorrect.  But, that's not a great reason to add more code just to make\nthings marginally less robust.",
  "id": "CVE-2026-98472",
  "modified": "2026-10-19T02:31:05.240128642Z",
  "published": "2026-10-18T15:15:24.654Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/12c1f6e03f944e399bd2c88441dca5dc702b95a5"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/6aef7cf800098749ff5d660222efaf6e01e98c09"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9784e5ca91b37b387f3f414af4340c54f7a63566"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98472.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98472"
    }
  ],
  "schema_version": "1.9.0",
  "summary": "KVM: SEV: Free have_run_cpus during VM destruction even if VM is no longer SEV"
}