CVE-2025-40124

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

HIGH
7.8
CVSS Score
Published: November 12, 2025 at 10:23 AM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: sparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC III Anthony Yznaga tracked down that a BUG_ON in ext4 code with large folios enabled resulted from copy_from_user() returning impossibly large values greater than the size to be copied. This lead to __copy_from_iter() returning impossible values instead of the actual number of bytes it was able to copy. The BUG_ON has been reported in https://lore.kernel.org/r/b14f55642207e63e907965e209f6323a0df6dcee.camel@physik.fu-berlin.de 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. The exception handlers expect that %o2 has already been masked during the bulk copy loop, but the masking was performed after that loop. This will fix the return value of copy_from_user and copy_to_user in the faulting case. The behaviour of memcpy stays unchanged.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.4.34 ≤ v < 4.54.8.10 ≤ v < 4.91c7e17b1c4d60cc5aa575460f7efb73686dd3b394.4.344.8.104.9ac663c54f40b2830b1ca32d1ae9d683fe248b14cee841d0aff649164080e445e84885015958d8ff4
Vendor states this is fixed in 1198077606aeffb102587c6ea079ce99641c99d4 (fixed)
Vendor states this is fixed in 1857cdca12c4aff58bf26a7005a4d02850c29927 (fixed)
Vendor states this is fixed in 47b49c06eb62504075f0f2e2227aee2e2c2a58b3 (fixed)
Vendor states this is fixed in 5ef9c94d7110e90260c06868cf1dcf899b9f25ee (fixed)
Vendor states this is fixed in 91eda032eb16e5d2be27c95584665bc555bb5a90 (fixed)
Vendor states this is fixed in dc766c4830a7e1e1ee9d7f77d4ab344f2eb23c8e (fixed)
Vendor states this is fixed in e50377c6b3f278c9f3ef017ffce17f5fcc9dace4 (fixed)
Vendor states this is fixed in fdd43fe6d286f27b826572457a89c926f97e2d3a (fixed)
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.9 (unaffected)
Vendor states this is fixed in 5.10.246 (unaffected)
Vendor states this is fixed in 5.15.195 (unaffected)
Vendor states this is fixed in 5.4.301 (unaffected)
Vendor states this is fixed in 6.1.156 (unaffected)
Vendor states this is fixed in 6.12.53 (unaffected)
Vendor states this is fixed in 6.17.3 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.112 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card