Skip to main content
VulnerabilityPublished Updated

CVE-2026-98140: Linux kernel · ntfs: fix kmap_local leak in write_mft_record_nolock() error paths

Source GCVE Database

0
Authoritative record:CVE-2026-98140· Medium

Not known to be exploited · CVSS 5.5 Medium : upgrade to cf06dcd572845723821b54a608fc2da995c3c8e2 or 5d7f7bf8fba8cf563b42b44aa4ab3d9928ac480c when convenient.

Data as of 26 Oct 2026, 22:27 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in cf06dcd572845723821b54a608fc2da995c3c8e2, 5d7f7bf8fba8cf563b42b44aa4ab3d9928ac480c
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade Linux kernel to cf06dcd572845723821b54a608fc2da995c3c8e2 or 5d7f7bf8fba8cf563b42b44aa4ab3d9928ac480c.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 115380f9a2f9675c7924563cbba70d40cae8fb81, < cf06dcd572845723821b54a608fc2da995c3c8e2
Fixed in
  • cf06dcd572845723821b54a608fc2da995c3c8e2
LinuxLinuxAffected
  • ≥ 115380f9a2f9675c7924563cbba70d40cae8fb81, < 5d7f7bf8fba8cf563b42b44aa4ab3d9928ac480c
Fixed in
  • 5d7f7bf8fba8cf563b42b44aa4ab3d9928ac480c
LinuxLinuxAffected
  • =7.1
Fixed in–

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.

References

Community reviews

Loading reviews…