Answer in brief
CVE-2025-38710 records a Unknown severity vulnerability in gfs2: Validate i_depth for exhash directories. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-38710 records a Unknown severity vulnerability in gfs2: Validate i_depth for exhash directories. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9a0045088d888c9c539c8c626a366cb52c0fbdab <076e992752e4b24178918f748d75597c80a408d2 || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <366183911b153e9b8cf758e1414e1154d7569337 || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <112bb60cd0e254a369e95aa9941a694ffeca089f || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <cddea0c721106ea480371412d8de21705eb27376 || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <53a0249d68a210c16e961b83adfa82f94ee0a53d || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <b5f46951e62377b6e406fadc18bc3c5bdf1632a7 || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <9680c58675b82348ab84d387e4fa727f7587e1a0 || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <557c024ca7250bb65ae60f16c02074106c2f197b | 076e992752e4b24178918f748d75597c80a408d2, 366183911b153e9b8cf758e1414e1154d7569337, 112bb60cd0e254a369e95aa9941a694ffeca089f, cddea0c721106ea480371412d8de21705eb27376, 53a0249d68a210c16e961b83adfa82f94ee0a53d, b5f46951e62377b6e406fadc18bc3c5bdf1632a7, 9680c58675b82348ab84d387e4fa727f7587e1a0, 557c024ca7250bb65ae60f16c02074106c2f197b |
| Linux/Linuxgeneric | 2.6.26 | Not reported |
Published upstream
Sep 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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'.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9a0045088d888c9c539c8c626a366cb52c0fbdab <076e992752e4b24178918f748d75597c80a408d2 || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <366183911b153e9b8cf758e1414e1154d7569337 || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <112bb60cd0e254a369e95aa9941a694ffeca089f || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <cddea0c721106ea480371412d8de21705eb27376 || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <53a0249d68a210c16e961b83adfa82f94ee0a53d || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <b5f46951e62377b6e406fadc18bc3c5bdf1632a7 || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <9680c58675b82348ab84d387e4fa727f7587e1a0 || >=9a0045088d888c9c539c8c626a366cb52c0fbdab <557c024ca7250bb65ae60f16c02074106c2f197b | 076e992752e4b24178918f748d75597c80a408d2, 366183911b153e9b8cf758e1414e1154d7569337, 112bb60cd0e254a369e95aa9941a694ffeca089f, cddea0c721106ea480371412d8de21705eb27376, 53a0249d68a210c16e961b83adfa82f94ee0a53d, b5f46951e62377b6e406fadc18bc3c5bdf1632a7, 9680c58675b82348ab84d387e4fa727f7587e1a0, 557c024ca7250bb65ae60f16c02074106c2f197b |
| Linux/Linuxgeneric | 2.6.26 | Not reported |
Published upstream
Sep 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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'.
Quoted source text, attributed separately from HOL analysis.