Home

Description

In the Linux kernel, the following vulnerability has been resolved: ntfs: ->d_compare() must not block ... so don't use __getname() there. Switch it (and ntfs_d_hash(), while we are at it) to kmalloc(PATH_MAX, GFP_NOWAIT). Yes, ntfs_d_hash() almost certainly can do with smaller allocations, but let ntfs folks deal with that - keep the allocation size as-is for now. Stop abusing names_cachep in ntfs, period - various uses of that thing in there have nothing to do with pathnames; just use k[mz]alloc() and be done with that. For now let's keep sizes as-in, but AFAICS none of the users actually want PATH_MAX.

PUBLISHED Reserved 2026-05-01 | Published 2026-05-06 | Updated 2026-05-08 | Assigner Linux




HIGH: 7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Product status

Default status
unaffected

a3a956c78efaa202b1d75190136671cf6e87bfbe (git) before 142c444a395f4d26055c8a4473e228bb86283f1e
affected

a3a956c78efaa202b1d75190136671cf6e87bfbe (git) before fb4b1f969ba01fa1d4088467a02fc1e5f0806710
affected

a3a956c78efaa202b1d75190136671cf6e87bfbe (git) before ca2a04e84af79596e5cd9cfe697d5122ec39c8ce
affected

Default status
affected

6.2
affected

Any version before 6.2
unaffected

6.18.16 (semver)
unaffected

6.19.6 (semver)
unaffected

7.0 (original_commit_for_fix)
unaffected

References

git.kernel.org/...c/142c444a395f4d26055c8a4473e228bb86283f1e

git.kernel.org/...c/fb4b1f969ba01fa1d4088467a02fc1e5f0806710

git.kernel.org/...c/ca2a04e84af79596e5cd9cfe697d5122ec39c8ce

cve.org (CVE-2026-43245)

nvd.nist.gov (CVE-2026-43245)

Download JSON