CVE-2026-89910 (GCVE-0-2026-89910)

Vulnerability from cvelistv5 – Published: 2026-09-16 10:32 – Updated: 2026-10-19 08:54
VLAI
Title
LoongArch: KVM: Fix uninitialized stack variable issue with dmsintc
Summary
In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Fix uninitialized stack variable issue with dmsintc Variable vector[] is declared on stack in function dmsintc_inject_irq() and sometimes it is used without initialized. Here fix this issue.
Assigner
Linux CNA under the mitre root
CNA scorecard D 53/100 over 6639 records in the last 180 days details
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 03de5eecb0f0f68f29086bc0075c7fd597bf4e4a , < f56060b0e10fa5633fac1dc243a25da3a5cdafb1 (git)
Affected: 03de5eecb0f0f68f29086bc0075c7fd597bf4e4a , < 81aa3a58b542ed88819115c80a17acd86eacb89d (git)
guessed Create a notification for this product.
Linux Linux Affected: 7.1
Unaffected: 0 , < 7.1 (semver)
Unaffected: 7.2.5 , ≤ 7.2.* (semver)
Unaffected: 7.3 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/loongarch/kvm/intc/dmsintc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "f56060b0e10fa5633fac1dc243a25da3a5cdafb1",
              "status": "affected",
              "version": "03de5eecb0f0f68f29086bc0075c7fd597bf4e4a",
              "versionType": "git"
            },
            {
              "lessThan": "81aa3a58b542ed88819115c80a17acd86eacb89d",
              "status": "affected",
              "version": "03de5eecb0f0f68f29086bc0075c7fd597bf4e4a",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/loongarch/kvm/intc/dmsintc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.1"
            },
            {
              "lessThan": "7.1",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.5",
              "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": "7.2.5",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: KVM: Fix uninitialized stack variable issue with dmsintc\n\nVariable vector[] is declared on stack in function dmsintc_inject_irq()\nand sometimes it is used without initialized. Here fix this issue."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.3,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The uninitialized vector[] is used in dmsintc_inject_irq(), called from kvm_deliver_intr() on KVM_RUN (kvm_pre_enter_guest) and KVM_GET_ONE_REG ESTAT after irqfd/KVM_SIGNAL_MSI or KVM_INTERRUPT queues INT_AVEC. That is a local /dev/kvm and guest MSI path, not a network or physical protocol handler.\nAC:L - A kvm-group VMM can create a MSGINT vCPU, queue INT_AVEC via KVM_INTERRUPT or irqfd MSI, then KVM_RUN or GET_ONE_REG ESTAT; any zero vector_map word leaves the matching stack slot uninitialized and typically nonzero. A guest retriggers the same inject on ordinary virtio/MSI I/O with no race.\nPR:L - kvm_dev_ioctl_create_vm() has no capable() check, so kvm-group (or equivalent) access is enough to create dmsintc, enable CPUCFG MSGINT, and inject AVEC. A LoongArch KVM tenant can also cause irqfd MSI injection and read guest ISR CSRs, which is Low privilege relative to the hypervisor, not init-namespace root.\nUI:N - The attacker issues KVM ioctls or guest device I/O themselves; no separate victim action such as mounting a filesystem or opening a file is required.\nS:C - dmsintc_inject_irq() writes host kernel stack contents into hardware guest ISR CSRs (LOONGARCH_CSR_ISR0-3) that the guest can read with csrrd and that the VMM can read after vcpu_put. That discloses hypervisor memory across the KVM guest-to-host boundary.\nC:H - Up to four uninitialized unsigned long stack slots are OR\u0027d into guest-visible ISR registers on every AVEC injection. Repeated MSI or KVM_RUN samples resample kernel stack including pointers, matching CNA stack-leak scoring for KASLR defeat.\nI:L - The same uninitialized words are OR\u0027d into guest ISR0-3, setting extra AVEC pending bits the VMM did not inject. That is limited corruption of guest interrupt-controller state, not an arbitrary host write or control-flow hijack.\nA:N - The uninitialized values are consumed only as ISR bitmasks via gcsr_write; they are not used as pointers and do not oops, panic, hang, or otherwise deny host service."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T08:54:43.786Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/f56060b0e10fa5633fac1dc243a25da3a5cdafb1"
        },
        {
          "url": "https://git.kernel.org/stable/c/81aa3a58b542ed88819115c80a17acd86eacb89d"
        }
      ],
      "title": "LoongArch: KVM: Fix uninitialized stack variable issue with dmsintc",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-89910",
    "datePublished": "2026-09-16T10:32:07.951Z",
    "dateReserved": "2026-09-11T19:38:34.774Z",
    "dateUpdated": "2026-10-19T08:54:43.786Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-89910",
      "date": "2026-11-10",
      "epss": "0.00151",
      "percentile": "0.04262"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "arch/loongarch/kvm/intc/dmsintc.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "f56060b0e10fa5633fac1dc243a25da3a5cdafb1",
                    "status": "affected",
                    "version": "03de5eecb0f0f68f29086bc0075c7fd597bf4e4a",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "81aa3a58b542ed88819115c80a17acd86eacb89d",
                    "status": "affected",
                    "version": "03de5eecb0f0f68f29086bc0075c7fd597bf4e4a",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "arch/loongarch/kvm/intc/dmsintc.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "7.1"
                  },
                  {
                    "lessThan": "7.1",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "7.2.*",
                    "status": "unaffected",
                    "version": "7.2.5",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "7.3",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: KVM: Fix uninitialized stack variable issue with dmsintc\n\nVariable vector[] is declared on stack in function dmsintc_inject_irq()\nand sometimes it is used without initialized. Here fix this issue."
          }
        ],
        "id": "CVE-2026-89910",
        "lastModified": "2026-10-19T09:18:36.433",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "LOCAL",
                "availabilityImpact": "NONE",
                "baseScore": 7.3,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "HIGH",
                "integrityImpact": "LOW",
                "privilegesRequired": "LOW",
                "scope": "CHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N",
                "version": "3.1"
              },
              "exploitabilityScore": 2.0,
              "impactScore": 4.7,
              "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
              "type": "Secondary"
            }
          ]
        },
        "published": "2026-09-16T11:17:00.027",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/81aa3a58b542ed88819115c80a17acd86eacb89d"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/f56060b0e10fa5633fac1dc243a25da3a5cdafb1"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-07T11:26:54+00:00",
      "cve": "CVE-2026-89910",
      "id": "CVE-2026-89910",
      "initial_release_date": "2026-09-16T00:00:00+00:00",
      "product_status:known_not_affected": "203",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: LoongArch: KVM: Fix uninitialized stack variable issue with dmsintc",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-89910.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.