CVE-2026-43245
In the Linux kernel, the following vulnerability has been resolved: ntfs: ->d_compare() must not block ... so don't use __getname() there.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.44%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.1
- 7.5 HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.44% probability · 37th percentile
- CISA KEV
- Not listed
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/02ecc0978c459fd90bb24b2a946dd16d43e68fe5
- https://git.kernel.org/stable/c/142c444a395f4d26055c8a4473e228bb86283f1ePatch
- https://git.kernel.org/stable/c/1be7ca86ce1794d966fda5d82181bc978b150fbc
- https://git.kernel.org/stable/c/ca2a04e84af79596e5cd9cfe697d5122ec39c8cePatch
- https://git.kernel.org/stable/c/fb4b1f969ba01fa1d4088467a02fc1e5f0806710Patch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.