# CVE-2025-40112: sparc: fix accurate exception reporting in copy_{from_to}_user for Niagara

> A flaw in SPARC kernel copy functions causes crashes due to incorrect exception handling, leading to denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Nov 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2025-40112, DEBIAN-CVE-2025-40112, GHSA-92f2-89hh-wf7v, ROOT-OS-DEBIAN-11-CVE-2025-40112, ROOT-OS-UBUNTU-2404-CVE-2025-40112, UBUNTU-CVE-2025-40112

## What is CVE-2025-40112?

CVE-2025-40112 is a high-severity vulnerability in Linux, published on 12 Nov 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:

sparc: fix accurate exception reporting in copy_{from_to}_user for Niagara

The referenced commit introduced exception handlers on user-space memory
references in copy_from_user and copy_to_user. These handlers return from
the respective function and calculate the remaining bytes left to copy
using the current register contents. This commit fixes a couple of bad
calculations and a broken epilogue in the exception handlers. This will
prevent crashes and ensure correct return values of copy_from_user and
copy_to_user in the faulting case. The behaviour of memcpy stays unchanged.

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


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

Apply the vendor's patch.

## Is CVE-2025-40112 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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