Description
In the Linux kernel, the following vulnerability has been resolved:

ntfs: fix kmap_local leak in write_mft_record_nolock() error paths

write_mft_record_nolock() maps the MFT record folio with
kmap_local_folio(), but the pre_write_mst_fixup() and
bio_add_folio() failure paths jump to the error label without
unmapping it. kmap_local mappings are stack-ordered per task, so
leaking one corrupts the nesting for any outer mapping.

Unmap the folio on those error paths too.
Published: 2026-09-25
Score: n/a
EPSS: n/a
KEV: No
Impact: Privilege Escalation
Action: Apply Patch
AI Analysis

Impact

The kernel bug occurs when ntfs drive handling fails to unmap a kmap_local page during certain error paths. Because kmap_local mappings are ordered per task, a single unmapped occurrence corrupts the stack ordering for all subsequent mappings in that context, which can lead to memory corruption or a kernel panic. This flaw allows an attacker to exploit the corrupted mapping order to manipulate kernel memory or cause a denial of service, effectively enabling privilege escalation or denial of service if the attacker can trigger the faulting path.

Affected Systems

The flaw exists in the Linux kernel for all variants of the Open Source Linux distribution. No specific kernel releases are listed in the available data, so any installation that has not applied the upstream patch that removes the missing unmap will be affected.

Risk and Exploitability

Without a published CVSS score the exact severity cannot be quantified, but the potential to corrupt kernel memory classifies this as a critical vulnerability. The EPSS score is not available and the flaw is not listed in the CISA KEV catalog at this time. Because the bug requires local execution inside the kernel context, the likely attack vector is a locally privileged process. Mitigation therefore requires applying the kernel update that implements the unmap change; no temporary work‑arounds are documented in the advisory.

Generated by OpenCVE AI on September 25, 2026 at 12:19 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest Linux kernel update that includes the fix for the kmap_local leak in write_mft_record_nolock()
  • If an immediate kernel upgrade is not possible, configure the system to limit untrusted code execution and enforce mandatory access control to reduce the risk of triggering the error paths
  • Verify the kernel configuration disables unnecessary NTFS support if the filesystem is not in use

Generated by OpenCVE AI on September 25, 2026 at 12:19 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 25 Sep 2026 12:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-772

Fri, 25 Sep 2026 10:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ntfs: fix kmap_local leak in write_mft_record_nolock() error paths write_mft_record_nolock() maps the MFT record folio with kmap_local_folio(), but the pre_write_mst_fixup() and bio_add_folio() failure paths jump to the error label without unmapping it. kmap_local mappings are stack-ordered per task, so leaking one corrupts the nesting for any outer mapping. Unmap the folio on those error paths too.
Title ntfs: fix kmap_local leak in write_mft_record_nolock() error paths
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-25T10:36:16.580Z

Reserved: 2026-09-25T10:25:14.319Z

Link: CVE-2026-98140

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-25T11:17:45.497

Modified: 2026-09-25T11:17:45.497

Link: CVE-2026-98140

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-25T12:30:08Z

Weaknesses
  • CWE-772

    Missing Release of Resource after Effective Lifetime