Kernel memory exposure via undersized file handle
Published May 1, 2025 · Updated May 11, 2026
Out-of-bounds read in the Linux isofs export code allows local users to expose kernel memory or crash the system via a short file handle. The isofs_fh_to_parent path reads the 16-byte parent_block member after handle_to_path allocates only the attacker-supplied 12-byte f_handle buffer. Reaching the read through open_by_handle_at requires CAP_DAC_READ_SEARCH; the reported consequence is a four-byte kernel out-of-bounds read that can disclose memory or interrupt service.
Summary
What happened
Out-of-bounds read in the Linux isofs export code allows local users to expose kernel memory or crash the system via a short file handle. The isofs_fh_to_parent path reads the 16-byte parent_block member after handle_to_path allocates only the attacker-supplied 12-byte f_handle buffer. Reaching the read through open_by_handle_at requires CAP_DAC_READ_SEARCH; the reported consequence is a four-byte kernel out-of-bounds read that can disclose memory or interrupt service.
The record
- CVE
- CVE-2025-37780
- Published
- May 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <007124c896e7d4614ac1f6bd4dedb975c35a2a8e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0405d4b63d082861f4eaff9d39c78ee9dc34f845
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0fdafdaef796816a9ed0fd7ac812932d569d9beb
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <56dfffea9fd3be0b3795a9ca6401e133a8427e0b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5e7de55602c61c8ff28db075cc49c8dd6989d7e0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <63d5a3e207bf315a32c7d16de6c89753a759f95a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <952e7a7e317f126d0a2b879fc531b716932d5ffa
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ee01a309ebf598be1ff8174901ed6e91619f1749
- Affected versionversion=2.6.12
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