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.
References (5)
Core 5
Core References
Scores
CVSS v3
7.5
EPSS
0.0006
EPSS Percentile
18.3%
Attack Vector
NETWORK
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Details
Status
published
Products (16)
Linux/Linux
< 6.2
Linux/Linux
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 - 142c444a395f4d26055c8a4473e228bb86283f1e
Linux/Linux
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 - ca2a04e84af79596e5cd9cfe697d5122ec39c8ce
Linux/Linux
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 - fb4b1f969ba01fa1d4088467a02fc1e5f0806710
Linux/Linux
6.12.91 - 6.12.*
Linux/Linux
6.18.16 - 6.18.*
Linux/Linux
6.19.6 - 6.19.*
Linux/Linux
6.2
Linux/Linux
6.6.141 - 6.6.*
Linux/Linux
7.0
... and 6 more
Published
May 06, 2026
Tracked Since
May 06, 2026