CVE-2025-40126
Description
In the Linux kernel, the following vulnerability has been resolved:
sparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC
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. This will fix the return value of copy_from_user and copy_to_user in the faulting case. The behaviour of memcpy stays unchanged.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A fix in the Linux kernel for SPARC corrects bad remainder calculations in copy_from_user/copy_to_user exception handlers on UltraSPARC.
In the Linux kernel's SPARC architecture, the copy_from_user and copy_to_user functions were instrumented with exception handlers that correctly return from faults. However, those handlers miscalculated the number of bytes not yet copied when a fault occurs [1]. This bug affects UltraSPARC CPUs and stems from improper use of register contents to compute the remaining length.
An attacker with local access could trigger a fault in these user-copy routines, and the erroneous byte-count calculation would cause the functions to return an incorrect leftover value to the caller [2]. No special privileges beyond user mode are needed to exercise the fault path; the vulnerability depends on the ability to provoke a page fault during a copy operation.
A wrong return value from copy_from_user or copy_to_user can lead to unintended data flow between kernel and user space — for example, the kernel may believe it copied more data than it actually did, potentially causing information leaks or memory corruption [3]. The memcpy function is not affected, as its behaviour remains unchanged.
Patches have been merged into the stable kernel tree to correct the arithmetic in the fault handlers [4]. Users running a SPARC-based Linux system should apply the latest updates to ensure accurate exception reporting. No workarounds have been published, but the fix is straightforward and available in the referenced commits.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
80bf3dc3a215641c18baee66159424dc0d0e09b137f277cc3674ff598148a7de3a75bbc8457c278500fce4fba17130011Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/0bf3dc3a2156f1c5ddaba4b85d09767874634114nvd
- git.kernel.org/stable/c/41c18baee66134e6ef786eb075c1b6adb22432b0nvd
- git.kernel.org/stable/c/4fba1713001195e59cfc001ff1f2837dab877efbnvd
- git.kernel.org/stable/c/57c278500fce3cd4e1c540700c0b05426a958393nvd
- git.kernel.org/stable/c/59424dc0d0e044b2eb007686a4724ddd91d57db5nvd
- git.kernel.org/stable/c/674ff598148a28bae0b5372339de56f2abf0b1d1nvd
- git.kernel.org/stable/c/7de3a75bbc8465d816336c74d50109e73501efabnvd
- git.kernel.org/stable/c/9b137f277cc3297044aabd950f589e505d30104cnvd
News mentions
0No linked articles in our index yet.