ntfs: protect runlist updates with the runlist lock
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: protect runlist updates with the runlist lock
ntfs_non_resident_attr_shrink() calls runlist helpers that require the runlist write lock, but did not hold it while freeing clusters and truncating the runlist. Serialize those operations and the resident conversion with the runlist lock.
ntfs_attr_map_cluster() can merge a newly allocated run before updating mapping pairs. If the update fails, free the clusters and restore both the in-memory runlist and on-disk mapping pairs from a saved runlist. Mark the volume in error if either rollback step fails.
From the CVE record · Linux
The Linux kernel’s ntfs code did not hold the required runlist write lock while freeing clusters and truncating a runlist. A mapping-pairs update failure could also leave the in-memory runlist and on-disk mapping pairs inconsistent. The input does not specify how an attacker could trigger these issues or whether access or user interaction is required.
Engineers running Linux kernels with ntfs support should check their deployments; affected versions are not specified.