# CVE-2025-68763: crypto: starfive - Correctly handle return of sg_nents_for_len

> An integer overflow in the StarFive crypto driver mishandles error codes, potentially leading to buffer overflows and system compromise.

- **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:** 5 Jan 2026
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-68763, DEBIAN-CVE-2025-68763, GHSA-28vg-cxp3-45wq, ROOT-OS-DEBIAN-13-CVE-2025-68763, ROOT-OS-UBUNTU-2404-CVE-2025-68763, UBUNTU-CVE-2025-68763

## What is CVE-2025-68763?

CVE-2025-68763 is a vulnerability in Linux, published on 5 Jan 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:

crypto: starfive - Correctly handle return of sg_nents_for_len

The return value of sg_nents_for_len was assigned to an unsigned long
in starfive_hash_digest, causing negative error codes to be converted
to large positive integers.

Add error checking for sg_nents_for_len and return immediately on
failure to prevent potential buffer overflows.

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


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

Apply the vendor's patch.

## Is CVE-2025-68763 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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