xfs: fix exchmaps reservation limit check
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:
xfs: fix exchmaps reservation limit check
xfs_exchmaps_estimate_overhead() adds the bmbt and rmapbt overhead to a local resblks variable, but the final UINT_MAX check still tests req->resblks. That is the reservation value from before the overhead was added.
The computed value is stored back in req->resblks and later passed to xfs_trans_alloc(), whose block reservation argument is unsigned int. Check the computed reservation so the existing limit applies to the value that will be used.
From the CVE record · Linux
In the Linux kernel's XFS exchmaps code, a reservation limit check tests the value before overhead is added, rather than the computed value passed to xfs_trans_alloc(). The input does not specify what an attacker could achieve or whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with XFS should check their exposure; affected versions are not specified.