xfs: resample the data fork mapping after cycling ILOCK
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3c68d44a2b49a0ac9165faa9c191e1e618c8a8d5 · < 44f891bc088958399eec27f7604928694aa35581| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
xfs: resample the data fork mapping after cycling ILOCK
xfs_reflink_fill_{cow_hole,delalloc} are both presented with an inode, a data fork mapping, and a cow fork mapping. Unfortunately, these two helpers cycle the ILOCK to grab a transaction, which means that the mappings are stale as soon as we reacquire the ILOCK. Currently we refresh the cow fork mapping by re-calling xfs_find_trim_cow_extent, but we don't refresh the data fork mapping beforehand, which means that the xfs_bmap_trim_cow in that function queries the refcount btree about the wrong physical blocks and returns an inaccurate value in *shared.
If *shared is now false, the directio write proceeds with a stale data fork mapping. Fix this by querying the data fork mapping if the sequence counter changes across the ILOCK cycle.
From the CVE record · Linux
XFS reflink helpers in the Linux kernel can use a stale data fork mapping after releasing and reacquiring ILOCK. During direct I/O writes, this can produce an inaccurate shared-block status and allow a write to proceed with the stale mapping. The input does not specify an authentication requirement or separate user interaction.
Engineers running Linux kernels with XFS should check their kernel version; affected versions are not specified.