gfs2: Validate i_depth for exhash directories
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.258, 5.15.209, 6.1.175, 6.6.134, 6.12.43, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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'.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 9a0045088d888c9c539c8c626a366cb52c0fbdab · fixed in 076e992752e4b24178918f748d75597c80a408d2; From 9a0045088d888c9c539c8c626a366cb52c0fbdab · fixed in 366183911b153e9b8cf758e1414e1154d7569337; From 9a0045088d888c9c539c8c626a366cb52c0fbdab · fixed in 112bb60cd0e254a369e95aa9941a694ffeca089f; From 9a0045088d888c9c539c8c626a366cb52c0fbdab · fixed in cddea0c721106ea480371412d8de21705eb27376; From 9a0045088d888c9c539c8c626a366cb52c0fbdab · fixed in 53a0249d68a210c16e961b83adfa82f94ee0a53d; From 9a0045088d888c9c539c8c626a366cb52c0fbdab · fixed in b5f46951e62377b6e406fadc18bc3c5bdf1632a7; From 9a0045088d888c9c539c8c626a366cb52c0fbdab · fixed in 9680c58675b82348ab84d387e4fa727f7587e1a0; From 9a0045088d888c9c539c8c626a366cb52c0fbdab · fixed in 557c024ca7250bb65ae60f16c02074106c2f197b
- Linux Linux
2.6.26
- KernelLinux
From 2.6.26 · fixed in 5.10.258; From 5.11.0 · fixed in 5.15.209; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.134; From 6.7.0 · fixed in 6.12.43; From 6.13.0 · fixed in 6.15.11; From 6.16.0 · fixed in 6.16.2
References 8
git.kernel.org
- stable/c/076e992752e4b24178918f748d75597c80a408d2
- stable/c/366183911b153e9b8cf758e1414e1154d7569337
- stable/c/112bb60cd0e254a369e95aa9941a694ffeca089f
- stable/c/cddea0c721106ea480371412d8de21705eb27376
- stable/c/53a0249d68a210c16e961b83adfa82f94ee0a53d
- stable/c/b5f46951e62377b6e406fadc18bc3c5bdf1632a7
- stable/c/9680c58675b82348ab84d387e4fa727f7587e1a0
- stable/c/557c024ca7250bb65ae60f16c02074106c2f197b