Kernel memory corruption via truncated OrangeFS file length
Published Jun 18, 2025 · Updated Aug 5, 2026
Memory corruption in the OrangeFS client in Linux allows local users to corrupt kernel memory through writes to an oversized file. On 32-bit kernels, orangefs_write_begin stores i_size_read() in a 32-bit ssize_t, truncating lengths above 4 GiB and creating a multi-gigabyte bvec that walks beyond the dirty page. An existing OrangeFS mount and write permission are required; the resulting out-of-bounds reads and writes disclose kernel memory or cause a kernel panic.
Summary
What happened
Memory corruption in the OrangeFS client in Linux allows local users to corrupt kernel memory through writes to an oversized file. On 32-bit kernels, orangefs_write_begin stores i_size_read() in a 32-bit ssize_t, truncating lengths above 4 GiB and creating a multi-gigabyte bvec that walks beyond the dirty page. An existing OrangeFS mount and write permission are required; the resulting out-of-bounds reads and writes disclose kernel memory or cause a kernel panic.
The record
- CVE
- CVE-2025-38065
- Published
- Jun 18, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record 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.6
- Affected versionversion=f7ab093f74bf638ed98fd1115f3efa17e308bb7f <062e8093592fb866b8e016641a8b27feb6ac509d
- Affected versionversion=f7ab093f74bf638ed98fd1115f3efa17e308bb7f <121f0335d91e46369bf55b5da4167d82b099a166
- Affected versionversion=f7ab093f74bf638ed98fd1115f3efa17e308bb7f <15602508ad2f923e228b9521960b4addcd27d9c4
- Affected versionversion=f7ab093f74bf638ed98fd1115f3efa17e308bb7f <2323b806221e6268a4e17711bc72e2fc87c191a3
- Affected versionversion=f7ab093f74bf638ed98fd1115f3efa17e308bb7f <341e3a5984cf5761f3dab16029d7e9fb1641d5ff
- Affected versionversion=f7ab093f74bf638ed98fd1115f3efa17e308bb7f <5111227d7f1f57f6804666b3abf780a23f44fc1d
- Affected versionversion=f7ab093f74bf638ed98fd1115f3efa17e308bb7f <cd918ec24168fe08c6aafc077dd3b6d88364c5cf
- Affected versionversion=f7ab093f74bf638ed98fd1115f3efa17e308bb7f <ceaf195ed285b77791e29016ee6344b3ded609b3
What conditions does exploitation require?
What is affected?
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