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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://git.kernel.org/stable/c/5d7f7bf8fba8cf563b42b44aa4ab3d9928ac480c Patch
- https://git.kernel.org/stable/c/cf06dcd572845723821b54a608fc2da995c3c8e2 Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 6
- CwesCWE-401NVD modified 2026-10-26 18:36
- Cpes+2 CPE criteria (now 2)NVD modified 2026-10-26 18:36
- StatusPublished → AnalyzedNVD modified 2026-10-26 18:36
- CVSS5.5 (v3.1, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)NVD modified 2026-10-26 18:36
- StatusUndergoing Analysis → PublishedNVD modified 2026-10-19 09:14
- First seenunscoredNVD modified 2026-10-19 10:18
Affected (CPE criteria) 2
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:7.3:rc1:*:*:*:*:*:*