# CVE-2026-89909: LoongArch: KVM: Free init resources if kvm_init() fails

> A resource leak in the Linux kernel's LoongArch KVM initialization allows local attackers to cause memory exhaustion and denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-89909, DEBIAN-CVE-2026-89909, GHSA-9g5j-xh66-prwm, UBUNTU-CVE-2026-89909

## What is CVE-2026-89909?

CVE-2026-89909 is a vulnerability in Linux, published on 16 Sep 2026. 

### Official description

In 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().

## Which versions are affected by CVE-2026-89909?


## How do I fix CVE-2026-89909?

Apply the vendor's patch.

## Is CVE-2026-89909 being exploited?

There is no known exploitation of CVE-2026-89909 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89909 and fix it if it is affected.

What it is: CVE-2026-89909 is a vulnerability in Linux, published on 16 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-89909 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89909/ (Markdown: https://insights.sbomify.com/CVE-2026-89909/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89909
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89909
- OSV: https://osv.dev/vulnerability/CVE-2026-89909

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89909/
Summaries are generated and may contain mistakes; the official description above is the record.