ntfs: fix kmap_local leak in write_mft_record_nolock() error paths
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s NTFS write_mft_record_nolock() function fails to unmap an MFT record folio when pre_write_mst_fixup() or bio_add_folio() fails. The leaked mapping can corrupt the nesting of other mappings in the same task. The input does not specify an attack route, authentication requirements, or user interaction.
Teams running Linux kernels with the affected NTFS code should check their versions; no affected version range is provided.