# CVE-2026-68183: firmware: stratix10-svc: fix memory leaks and list corruption bugs

> A memory leak and list corruption bug in the Stratix10 service driver can cause kernel instability or crashes, requiring a patch.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** AZL-94871, BELL-CVE-2026-68183, DEBIAN-CVE-2026-68183, GHSA-5m2j-mq9f-gqm6, UBUNTU-CVE-2026-68183

## What is CVE-2026-68183?

CVE-2026-68183 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:

firmware: stratix10-svc: fix memory leaks and list corruption bugs

Fix a memory leak when gen_pool_alloc() fails by freeing pmem on the error
path. Switch pmem allocation from devm_kzalloc() to kzalloc() with
explicit kfree() in the free path to match its list-managed lifetime.
Remove the erroneous list_del(&svc_data_mem) which corrupted the list head
on failed lookups.

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


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

Apply the vendor's patch.

## Is CVE-2026-68183 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68183 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-68183 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-68183/ (Markdown: https://insights.sbomify.com/CVE-2026-68183/index.md)
```

## Sources

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

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