CVE-2025-38710
What it is
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'.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 6.12.43
- Linux Kernel < 6.15.11
- Linux Kernel < 6.16.2
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38710.md and follow it. Check whether this project is affected by CVE-2025-38710. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/53a0249d68a210c16e961b83adfa82f94ee0a53d
- https://git.kernel.org/stable/c/557c024ca7250bb65ae60f16c02074106c2f197b
- https://git.kernel.org/stable/c/9680c58675b82348ab84d387e4fa727f7587e1a0
- https://git.kernel.org/stable/c/b5f46951e62377b6e406fadc18bc3c5bdf1632a7
References
- https://git.kernel.org/stable/c/076e992752e4b24178918f748d75597c80a408d2
- https://git.kernel.org/stable/c/112bb60cd0e254a369e95aa9941a694ffeca089f
- https://git.kernel.org/stable/c/366183911b153e9b8cf758e1414e1154d7569337
- https://git.kernel.org/stable/c/53a0249d68a210c16e961b83adfa82f94ee0a53d
- https://git.kernel.org/stable/c/557c024ca7250bb65ae60f16c02074106c2f197b
- https://git.kernel.org/stable/c/9680c58675b82348ab84d387e4fa727f7587e1a0
- https://git.kernel.org/stable/c/b5f46951e62377b6e406fadc18bc3c5bdf1632a7
- https://git.kernel.org/stable/c/cddea0c721106ea480371412d8de21705eb27376