Kernel memory corruption via unchecked exhash depth
Published Sep 4, 2025 · Updated Aug 5, 2026
Improper validation in the GFS2 filesystem in Linux allows local users to corrupt kernel memory by accessing a crafted volume. gfs2_dinode_in accepts an exhash directory i_depth of zero, so dir_e_read shifts by 32 and derives an attacker-chosen out-of-bounds index. The crafted filesystem must be mounted, normally requiring CAP_SYS_ADMIN or delegated mounting; a lookup can expose kernel data, misdirect metadata writes, hang the mount, or panic the kernel.
Summary
What happened
Improper validation in the GFS2 filesystem in Linux allows local users to corrupt kernel memory by accessing a crafted volume. gfs2_dinode_in accepts an exhash directory i_depth of zero, so dir_e_read shifts by 32 and derives an attacker-chosen out-of-bounds index. The crafted filesystem must be mounted, normally requiring CAP_SYS_ADMIN or delegated mounting; a lookup can expose kernel data, misdirect metadata writes, hang the mount, or panic the kernel.
The record
- CVE
- CVE-2025-38710
- Published
- Sep 4, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 4, 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=2.6.26
- Affected versionversion=9a0045088d888c9c539c8c626a366cb52c0fbdab <076e992752e4b24178918f748d75597c80a408d2
- Affected versionversion=9a0045088d888c9c539c8c626a366cb52c0fbdab <112bb60cd0e254a369e95aa9941a694ffeca089f
- Affected versionversion=9a0045088d888c9c539c8c626a366cb52c0fbdab <366183911b153e9b8cf758e1414e1154d7569337
- Affected versionversion=9a0045088d888c9c539c8c626a366cb52c0fbdab <53a0249d68a210c16e961b83adfa82f94ee0a53d
- Affected versionversion=9a0045088d888c9c539c8c626a366cb52c0fbdab <557c024ca7250bb65ae60f16c02074106c2f197b
- Affected versionversion=9a0045088d888c9c539c8c626a366cb52c0fbdab <9680c58675b82348ab84d387e4fa727f7587e1a0
- Affected versionversion=9a0045088d888c9c539c8c626a366cb52c0fbdab <b5f46951e62377b6e406fadc18bc3c5bdf1632a7
- Affected versionversion=9a0045088d888c9c539c8c626a366cb52c0fbdab <cddea0c721106ea480371412d8de21705eb27376
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