GHSA-9G5J-XH66-PRWM
Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 12:30In the Linux kernel, the following vulnerability has been resolved:
LoongArch: KVM: Free init resources if kvm_init() fails
kvm_loongarch_init() calls kvm_loongarch_env_init() to allocate the per-CPU kvm_context (vmcs) and kvm_loongarch_ops and to register the perf callbacks, and then calls kvm_init(). If kvm_init() fails its result is returned directly, but since module_init() does not run the module_exit() stuff on failure, so kvm_loongarch_env_exit() is never called and those resources are leaked.
So call kvm_loongarch_env_exit() when kvm_init() fails, matching the teardown-on-failure pattern used by riscv_kvm_init().
{
"affected": [],
"aliases": [
"CVE-2026-89909"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-16T11:16:59Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: KVM: Free init resources if kvm_init() fails\n\nkvm_loongarch_init() calls kvm_loongarch_env_init() to allocate the\nper-CPU kvm_context (vmcs) and kvm_loongarch_ops and to register the\nperf callbacks, and then calls kvm_init(). If kvm_init() fails its\nresult is returned directly, but since module_init() does not run the\nmodule_exit() stuff on failure, so kvm_loongarch_env_exit() is never\ncalled and those resources are leaked.\n\nSo call kvm_loongarch_env_exit() when kvm_init() fails, matching the\nteardown-on-failure pattern used by riscv_kvm_init().",
"id": "GHSA-9g5j-xh66-prwm",
"modified": "2026-09-16T12:30:41Z",
"published": "2026-09-16T12:30:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89909"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3bf6f5e2e1007d38a5f35bd37e94ab645a0c40bc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6b78786ee7260d9818cf1d7a245b7a655ef83076"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6bbbd7b719233645a5c120557a9ca1422e6b7a48"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f7a1064cce3b100b54780c68529176232d8eb01e"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.