CVE-2025-38065: orangefs: Do not truncate file size
In the Linux kernel, the following vulnerability has been resolved:
orangefs: Do not truncate file size
'len' is used to store the result of i_size_read(), so making 'len'
a size_t results in truncation to 4GiB on 32-bit systems.
Security readout for executives and security teams
Plain-English summary
A Linux OrangeFS flaw can misread file sizes larger than 4 GiB on 32-bit systems because a value is stored in a type that is too small. This may cause incorrect file handling. The supplied CVSS rating is 7.8, although the public description does not establish the precise path to confidentiality, integrity, and availability loss.
Executive priority
Prioritize remediation for 32-bit systems actively using OrangeFS; broader emergency action is not supported by the supplied evidence. The high CVSS score warrants timely patching, but exposure is configuration-dependent and active exploitation is not reported. Ask infrastructure teams for an inventory and distributor-confirmed patch status.
Technical view
The OrangeFS kernel code stored the result of i_size_read() in a size_t. On 32-bit systems, that type can truncate a larger file size at the 4 GiB boundary. Linux stable commits change the handling to preserve the file size. The supplied record identifies local, low-privilege attack conditions, but provides no trigger or impact-chain details.
Likely exposure
Exposure appears limited to affected 32-bit Linux kernels where OrangeFS is present and used, particularly with files exceeding 4 GiB. Systems running only 64-bit kernels or not using OrangeFS are less likely to encounter the described condition. The supplied version list is ambiguous, so distributor-specific package status should determine applicability.
Exploitation context
The supplied record is not listed in KEV, and no cited source reports active exploitation or a public exploit. The CVSS vector describes local access with low privileges and no user interaction. Treat exploitation status as unconfirmed rather than assuming the flaw is being used in attacks.
Researcher notes
The central condition is integer-width truncation of i_size_read() output on 32-bit systems. The bundle does not identify a CWE, demonstrate memory corruption, explain the full security impact, or provide reliable affected-version ranges. Validate against the relevant stable commit and distributor backport rather than relying solely on upstream version numbers.
Mitigation direction
Install a supported vendor kernel containing the applicable Linux stable fix.
Prioritize affected 32-bit hosts that actively mount or use OrangeFS.
Consult Linux distributor advisories to map patched kernel package versions accurately.
If updates are delayed, avoid affected OrangeFS workloads involving files larger than 4 GiB.
Validation and detection
Inventory kernel architecture and version across systems using OrangeFS.
Confirm whether OrangeFS is installed, mounted, or operationally required.
Check distributor package advisories for explicit CVE-2025-38065 remediation status.
After updating, verify the running kernel matches the installed patched package.
Safely test large-file handling in a non-production OrangeFS environment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CVE-2025-38065 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
1ADP providers
11Source links
CVSS vector scores
1 official score
We 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.