{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.2.10-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  KVM: SVM: Update control fields on #VMEXIT if and only if VMRUN succeeded  Leave control.erap_ctl and control.clean as-is in the VMCS if VMRUN fails, because as per AMD:    there's no explicit architectural guarantee about the behavior in the   presence of VMRUN failures. So the best thing to do would be to assume   that if VMRUN fails, the actions requested in the control fields may not   have been performed.",
  "id": "DEBIAN-CVE-2026-98714",
  "modified": "2026-10-19T04:47:31.013016924Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-98714"
    }
  ],
  "upstream": [
    "CVE-2026-98714"
  ]
}