Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw on SPARC Niagara systems can mishandle faults while copying data between user and kernel memory. The resulting incorrect calculations or broken return path may crash the system or produce incorrect copy results. An attacker requires local, low-privileged access; this is not described as a remotely exploitable issue.
Executive priority
Treat this as high priority for organizations operating multi-user or untrusted workloads on SPARC Niagara Linux. For environments without that architecture, urgency is low after inventory confirms non-exposure. Focus on accurate asset identification and vendor-supported kernel updates; there is no supplied evidence of active exploitation.
Technical view
Exception handlers in SPARC Niagara copy_from_user and copy_to_user used incorrect remaining-byte calculations and contained a broken epilogue. Faulting user-memory accesses could therefore crash the kernel or return incorrect results. The supplied CVSS 3.1 score is 7.8, with local access, low complexity, low privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact.
Likely exposure
Exposure appears limited to Linux systems using affected SPARC Niagara code, substantially narrowing typical enterprise impact. The supplied version records are ambiguous and include commit identifiers alongside release numbers. Confirm architecture, running kernel build, distribution backports, and inclusion of a referenced stable fix rather than relying solely on version-string comparison.
Exploitation context
The supplied record does not establish active exploitation, and the CVE is not identified as being in KEV. The CVSS vector requires local access and low privileges. Public sources provided here describe the defect and fixes, but provide no evidence of a public exploit or observed attacks.
Researcher notes
The security consequence beyond crashes and incorrect copy return values is not demonstrated in the supplied narrative, despite the CVSS assigning high impact across all three categories. Version metadata is difficult to interpret and should not be normalized without vendor confirmation. memcpy behavior is explicitly unchanged. Avoid inferring exploitability from the CVSS score alone.
Mitigation direction
- Prioritize inventory and patching of SPARC Niagara systems running potentially affected Linux kernels.
- Install a vendor-supported kernel containing the applicable referenced stable fix.
- Restrict local accounts and untrusted workload access until affected systems are updated.
- Consult distribution guidance where kernel version numbers may conceal backported fixes.
Validation and detection
- Confirm whether each system uses SPARC Niagara hardware and the affected copy-user implementation.
- Record the running kernel release, package revision, architecture, and distribution.
- Verify the installed kernel contains the applicable referenced stable commit or vendor backport.
- After updating, confirm the patched kernel is running following any required reboot.
- Review kernel logs for unexplained faults or crashes; these alone do not prove exploitation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2025-40112 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/05440320ea3e249d5f984918f2bf51210c1a7c03CVE reference, Linux
- https://git.kernel.org/stable/c/7823fc4d8ab5e57f8db7806ff2530c03c166c4bbCVE reference, Linux
- https://git.kernel.org/stable/c/37547d8e6eba87507279ee3dfddfd9dc46335454CVE reference, Linux
- https://git.kernel.org/stable/c/a365ee556e45f780ee322b349a06efdad0c1458fCVE reference, Linux
- https://git.kernel.org/stable/c/8cdeb5e482d3fdce7e825444b6ca3865e24c0228CVE reference, Linux
- https://git.kernel.org/stable/c/a90ce516a73dbe087f9bf3dbf311301a58d125c6CVE reference, Linux
- https://git.kernel.org/stable/c/088c5098ec6d6b0396edfbf3dad3e81de8469c1cCVE reference, Linux
- https://git.kernel.org/stable/c/0b67c8fc10b13a9090340c5f8a37d308f4e1571cCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.