CVE-2025-40112 json
sparc: fix accurate exception reporting in copy_{from_to}_user for Niagara
published 11mo ago modified 21d ago also EUVD-2025-124970
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 4.5, 4.9, 5.4.301, 5.10.246, 5.15.195, 6.1.156, 6.6.112, 6.12.53, 6.17.3, 6.18
- linux Debian 12 6.1.158-1
- linux Debian 13 6.12.57-1
- linux Debian 14 6.17.6-1
debian advisories DEBIAN-CVE-2025-40112
- linux Ubuntu 22.04 LTS 5.15.0-170.180
- linux Ubuntu 24.04 LTS 6.8.0-106.106
- linux Ubuntu 25.10 6.17.0-14.14
- linux-aws Ubuntu 22.04 LTS 5.15.0-1100.107
- linux-aws Ubuntu 24.04 LTS 6.8.0-1050.53
- linux-aws Ubuntu 25.10 6.17.0-1007.7
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1100.109
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1052.55
ubuntu advisories UBUNTU-CVE-2025-40112
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/05440320ea3e249d5f984918f2bf51210c1a7c03 commit
- git.kernel.org/stable/c/7823fc4d8ab5e57f8db7806ff2530c03c166c4bb commit
- git.kernel.org/stable/c/37547d8e6eba87507279ee3dfddfd9dc46335454 commit
- git.kernel.org/stable/c/a365ee556e45f780ee322b349a06efdad0c1458f commit
- git.kernel.org/stable/c/8cdeb5e482d3fdce7e825444b6ca3865e24c0228 commit
- git.kernel.org/stable/c/a90ce516a73dbe087f9bf3dbf311301a58d125c6 commit
- git.kernel.org/stable/c/088c5098ec6d6b0396edfbf3dad3e81de8469c1c commit
- git.kernel.org/stable/c/0b67c8fc10b13a9090340c5f8a37d308f4e1571c commit
Is CVE-2025-40112 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/05440320ea3e249d5f984918f2bf51210c1a7c03
- git.kernel.org /stable/c/7823fc4d8ab5e57f8db7806ff2530c03c166c4bb
- git.kernel.org /stable/c/37547d8e6eba87507279ee3dfddfd9dc46335454
- git.kernel.org /stable/c/a365ee556e45f780ee322b349a06efdad0c1458f
- git.kernel.org /stable/c/8cdeb5e482d3fdce7e825444b6ca3865e24c0228
- git.kernel.org /stable/c/a90ce516a73dbe087f9bf3dbf311301a58d125c6
- git.kernel.org /stable/c/088c5098ec6d6b0396edfbf3dad3e81de8469c1c
- git.kernel.org /stable/c/0b67c8fc10b13a9090340c5f8a37d308f4e1571c
Sources
- CVE List CVE-2025-40112
- NVD CVE-2025-40112
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.