Kernel crash via faulty SPARC copy epilogue
Published Nov 12, 2025 · Updated Nov 12, 2025
Improper exception handling in Linux kernels using SPARC Niagara copy routines allows local users to crash the kernel via a faulting user pointer. In arch/sparc/lib/NGmemcpy.S, exception handlers miscalculate the remaining byte count and return without restoring the register window. An unprivileged local process can trigger the fault through ordinary system calls; the documented consequences are a kernel crash and incorrect copy return values.
Summary
What happened
Improper exception handling in Linux kernels using SPARC Niagara copy routines allows local users to crash the kernel via a faulting user pointer. In arch/sparc/lib/NGmemcpy.S, exception handlers miscalculate the remaining byte count and return without restoring the register window. An unprivileged local process can trigger the fault through ordinary system calls; the documented consequences are a kernel crash and incorrect copy return values.
The record
- CVE
- CVE-2025-40112
- Published
- Nov 12, 2025
- Updated
- Nov 12, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 12, 2025CVE publishedPublication date reported by the CVE source.
- Nov 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.9
- Affected versionversion=7ae3aaf53f1695877ccd5ebbc49ea65991e41f1e <05440320ea3e249d5f984918f2bf51210c1a7c03
- Affected versionversion=7ae3aaf53f1695877ccd5ebbc49ea65991e41f1e <088c5098ec6d6b0396edfbf3dad3e81de8469c1c
- Affected versionversion=7ae3aaf53f1695877ccd5ebbc49ea65991e41f1e <0b67c8fc10b13a9090340c5f8a37d308f4e1571c
- Affected versionversion=7ae3aaf53f1695877ccd5ebbc49ea65991e41f1e <37547d8e6eba87507279ee3dfddfd9dc46335454
- Affected versionversion=7ae3aaf53f1695877ccd5ebbc49ea65991e41f1e <7823fc4d8ab5e57f8db7806ff2530c03c166c4bb
- Affected versionversion=7ae3aaf53f1695877ccd5ebbc49ea65991e41f1e <8cdeb5e482d3fdce7e825444b6ca3865e24c0228
- Affected versionversion=7ae3aaf53f1695877ccd5ebbc49ea65991e41f1e <a365ee556e45f780ee322b349a06efdad0c1458f
- Affected versionversion=7ae3aaf53f1695877ccd5ebbc49ea65991e41f1e <a90ce516a73dbe087f9bf3dbf311301a58d125c6
- Affected versionversion=a15859f9d8396cce7c55ccdb7e75f70f14cbc349
- Affected versionversion=bfc8be6593097cb074d3912ba2f27565cfbb7d6e
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo