# CVE-2026-68084: staging: vme_user: fix location monitor leak in tsi148 bridge

> A memory leak in the Linux kernel vme_user driver allows local attackers to cause denial of service by exhausting kernel memory during device unbind.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68084, DEBIAN-CVE-2026-68084, GHSA-wq22-gq55-wmwf, UBUNTU-CVE-2026-68084

## What is CVE-2026-68084?

CVE-2026-68084 is a memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

staging: vme_user: fix location monitor leak in tsi148 bridge

tsi148_probe() allocates a location monitor resource and links it into
tsi148_bridge->lm_resources. The probe error path frees this list, but
tsi148_remove() only frees the dma, slave and master resource lists, so
the location monitor resource is leaked on device unbind or module
unload.

Free the lm_resources list in tsi148_remove() as well, before
tsi148_bridge is freed.

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


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

Apply the vendor's patch.

## Is CVE-2026-68084 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68084 is a memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68084 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-68084/ (Markdown: https://insights.sbomify.com/CVE-2026-68084/index.md)
```

## Sources

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

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