CVE-2026-98140·Kernel vulnerability
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.
- Severity
- medium
- Software
- Kernel
- Fixed in
- 7.2.7
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.10% — in the bottom 1% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 7.1
Until: 7.2.7
Fixed in: 7.2.7
How to fix this CVE
Update your Linux kernel to version 7.2.7 or later to resolve a memory mapping leak in the NTFS write operation handler. This vulnerability causes improper cleanup of kernel memory mappings during error conditions, which can corrupt the kernel's internal state and lead to system instability. Applying the kernel patch ensures that all memory mappings are properly released regardless of write operation success or failure.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check your current kernel version: uname -r
- Verify if NTFS is mounted on your system: mount | grep -i ntfs or cat /etc/fstab | grep -i ntfs
- Review kernel logs for memory mapping warnings: sudo dmesg | grep -i 'kmap\|mapping\|leak'
- After updating, reboot and verify new kernel version: uname -r (should be 7.2.7 or later)
- Confirm the fix is present: grep -i 'write_mft_record_nolock' /boot/config-$(uname -r) or systemmap check
FAQ
What is CVE-2026-98140?
This vulnerability is a memory mapping resource leak in the Linux kernel's NTFS file system driver, specifically in the write_mft_record_nolock() function. When write operations encounter certain error conditions, the kernel fails to properly unmapped memory, corrupting the kernel's stack-ordered mapping state for subsequent operations.
Is CVE-2026-98140 being actively exploited?
No, this vulnerability is not currently listed in CISA's Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, systems with NTFS mounted should still prioritize patching to prevent potential denial-of-service scenarios.
What versions of Kernel are affected by CVE-2026-98140?
Linux kernel versions 7.1 through 7.2.6 are vulnerable. The vulnerability has been fixed in kernel version 7.2.7 and later.
How do I check if my server is vulnerable to CVE-2026-98140?
Run 'uname -r' to check your kernel version. If it shows version 7.1.x or 7.2.0 through 7.2.6, your system is vulnerable, especially if NTFS partitions are mounted (check with 'mount | grep ntfs').
Does Defensia detect CVE-2026-98140?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-98140 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-98140. Free for 1 server.
Get started free