ntfs: fix kmap_local leak in write_mft_record_nolock() error paths
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5d7f7bf8fba8cf563b42b44aa4ab3d9928ac480c and Kernel cf06dcd572845723821b54a608fc2da995c3c8e2.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.1, >=115380f9a2f9675c7924563cbba70d40cae8fb81 <5d7f7bf8fba8cf563b42b44aa4ab3d9928ac480c, >=115380f9a2f9675c7924563cbba70d40cae8fb81 <cf06dcd572845723821b54a608fc2da995c3c8e2 | 5d7f7bf8fba8cf563b42b44aa4ab3d9928ac480c, cf06dcd572845723821b54a608fc2da995c3c8e2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket