# CVE-2025-68328: firmware: stratix10-svc: fix bug in saving controller data

> A bug in the Stratix10 service driver causes a kernel panic during module removal, leading to denial of service for local privileged users.

- **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:** 22 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-68328, DEBIAN-CVE-2025-68328, GHSA-p94w-2mf4-q2mj, ROOT-OS-DEBIAN-12-CVE-2025-68328, ROOT-OS-DEBIAN-13-CVE-2025-68328, ROOT-OS-UBUNTU-2204-CVE-2025-68328, ROOT-OS-UBUNTU-2404-CVE-2025-68328, UBUNTU-CVE-2025-68328

## What is CVE-2025-68328?

CVE-2025-68328 is a vulnerability in Linux, published on 22 Dec 2025. 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 bug in saving controller data

Fix the incorrect usage of platform_set_drvdata and dev_set_drvdata. They
both are of the same data and overrides each other. This resulted in the
rmmod of the svc driver to fail and throw a kernel panic for kthread_stop
and fifo free.

## Which versions are affected by CVE-2025-68328?


## How do I fix CVE-2025-68328?

Apply the vendor's patch.

## Is CVE-2025-68328 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68328 and fix it if it is affected.

What it is: CVE-2025-68328 is a vulnerability in Linux, published on 22 Dec 2025. 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-2025-68328 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-2025-68328/ (Markdown: https://insights.sbomify.com/CVE-2025-68328/index.md)
```

## Sources

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

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