CVE-2025-38710
Last modified
CVE-2025-38710 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: gfs2: Validate i_depth for exhash directories A fuzzer test introduced corruption that ends up with a depth of 0 in dir_e_read(), causing an undefined shift by 32 at: index = hash >> (32 - dip->i_depth); As calculated in an open-coded way in dir_make_exhash(), the minimum depth for an exhash directory is ilog2(sdp->sd_hash_ptrs) and 0 is invalid as sdp->sd_hash_ptrs is fixed as sdp->bsize / 16 at mount time. So we can avoid the undefined behaviour by checking for depth values lower than the minimum in gfs2_dinode_in(). Values greater than the maximum are already being checked for there. Also switch the calculation in dir_make_exhash() to use ilog2() to clarify how the depth is calculated. Tested with the syzkaller repro.c and xfstests '-g quick'.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: gfs2: Validate i_depth for exhash directories A fuzzer test introduced corruption that ends up with a depth of 0 in dir_e_read(), causing an undefined shift by 32 at: index = hash >> (32 - dip->i_depth); As calculated in an open-coded way in dir_make_exhash(), the minimum depth for an exhash directory is ilog2(sdp->sd_hash_ptrs) and 0 is invalid as sdp->sd_hash_ptrs is fixed as sdp->bsize / 16 at mount time. So we can avoid the undefined behaviour by checking for depth values lower than the minimum in gfs2_dinode_in(). Values greater than the maximum are already being checked for there. Also switch the calculation in dir_make_exhash() to use ilog2() to clarify how the depth is calculated. Tested with the syzkaller repro.c and xfstests '-g quick'.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | < 6.12.43 |
| Linux | Linux Kernel | >= 6.13, < 6.15.11 |
| Linux | Linux Kernel | >= 6.16, < 6.16.2 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-38710?
How severe is CVE-2025-38710?
How do I fix CVE-2025-38710?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-38705In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38706In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38707In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38708In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38709In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3871Broken access control in Fortra's GoAnywhere MFT prior to 7.…5.3
- CVE-2025-38711In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38712In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38713In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-38714In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-38715In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-38716In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-38710?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
