LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43245: ntfs: ->d_compare() must not block

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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux NTFS filesystem operation could perform a blocking memory allocation where blocking is unsafe, potentially causing a system availability failure. The supplied assessment rates this high severity, with no stated confidentiality or integrity impact. Systems using affected kernels and NTFS functionality warrant prompt review.

Executive priority

Treat as a high-priority availability issue, especially for critical Linux systems using NTFS. Schedule vendor-supported kernel remediation promptly, but do not characterize it as actively exploited. Validate actual exposure because the provided version ranges and remote attack path are insufficiently explained.

Technical view

The NTFS dentry comparison path used __getname(), which may block. The resolution replaces names_cachep usage with kmalloc or kzalloc and uses kmalloc(PATH_MAX, GFP_NOWAIT) in ntfs_d_compare() and ntfs_d_hash(). The stated impact is availability loss; the bundle does not describe the exact failure mode or triggering prerequisites.

Likely exposure

Potential exposure includes Linux systems running the listed affected releases, particularly where NTFS filesystem operations are used. The supplied version data is ambiguous and includes unusual entries, so administrators should map distribution kernel builds and backports against the cited stable commits rather than relying only on version strings.

Exploitation context

The CVSS assessment states network-accessible, low-complexity, unauthenticated availability impact. However, the supplied technical description does not explain how a remote actor reaches the NTFS path. CISA KEV status is false, and no cited evidence establishes active exploitation or a public exploit.

Researcher notes

The core defect concerns sleeping allocation behavior in d_compare(), with related cleanup in ntfs_d_hash() and other names_cachep users. The source bundle provides multiple stable commits but no CWE, proof of concept, crash trace, attack prerequisites, or clear introduction and fixed-version ranges. The network CVSS vector requires further vendor confirmation.

Mitigation direction

  • Install a vendor-supported kernel update incorporating the applicable cited stable fix.
  • Check distribution security guidance for affected build and backport mappings.
  • Prioritize systems using NTFS or processing NTFS-backed storage.
  • Follow vendor guidance if an immediate kernel update is unavailable.

Validation and detection

  • Inventory deployed kernel builds and identify systems using NTFS.
  • Compare each vendor build against the cited stable fixes or documented backports.
  • Confirm updated systems booted into the remediated kernel.
  • Review vendor advisories for revised affected-version or exposure details.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-43245 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-43245Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa3a956c78efaa202b1d75190136671cf6e87bfbe, a3a956c78efaa202b1d75190136671cf6e87bfbe, a3a956c78efaa202b1d75190136671cf6e87bfbe, a3a956c78efaa202b1d75190136671cf6e87bfbe, a3a956c78efaa202b1d75190136671cf6e87bfbeunaffected
LinuxLinux6.2, 0, 6.6.141, 6.12.91, 6.18.16, 6.19.6, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.