CVE-2026-43245: Linux kernel · ntfs: ->d_compare() must not block
Source GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 27 Oct 2026, 00:07 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
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
- nvd.nist.gov/vuln/detail/CVE-2026-43245 (opens in a new tab)
- git.kernel.org/stable/c/142c444a395f4d26055c8a4473e228bb86283f1e (opens in a new tab)
- git.kernel.org/stable/c/ca2a04e84af79596e5cd9cfe697d5122ec39c8ce (opens in a new tab)
- git.kernel.org/stable/c/fb4b1f969ba01fa1d4088467a02fc1e5f0806710 (opens in a new tab)