CVE-2025-38710High· 7.8▾ TwilightIn 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: …
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 42.9 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 15.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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'.
Linux >= 9a0045088d888c9c539c8c626a366cb52c0fbdab < 076e992752e4b24178918f748d75597c80a408d2Linux >= 9a0045088d888c9c539c8c626a366cb52c0fbdab < 366183911b153e9b8cf758e1414e1154d7569337Linux >= 9a0045088d888c9c539c8c626a366cb52c0fbdab < 112bb60cd0e254a369e95aa9941a694ffeca089fLinux >= 9a0045088d888c9c539c8c626a366cb52c0fbdab < cddea0c721106ea480371412d8de21705eb27376Linux >= 9a0045088d888c9c539c8c626a366cb52c0fbdab < 53a0249d68a210c16e961b83adfa82f94ee0a53dLinux >= 9a0045088d888c9c539c8c626a366cb52c0fbdab < b5f46951e62377b6e406fadc18bc3c5bdf1632a7Linux >= 9a0045088d888c9c539c8c626a366cb52c0fbdab < 9680c58675b82348ab84d387e4fa727f7587e1a0Linux >= 9a0045088d888c9c539c8c626a366cb52c0fbdab < 557c024ca7250bb65ae60f16c02074106c2f197bLinux 2.6.26Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets