xfs: fix log recovery buffer allocation for the legacy h_size fixup
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 log recovery buffer allocation for the legacy h_size fixup
Commit a70f9fe52daa ("xfs: detect and handle invalid iclog size set by mkfs") added a fixup for incorrect h_size values used for the initial umount record in old xfsprogs versions. Later commit 0c771b99d6c9 ("xfs: clean up calculation of LR header blocks") cleaned up the log reover buffer calculation, but stoped using the fixed up h_size value to size the log recovery buffer, which can lead to an out of bounds access when the incorrect h_size does not come from the old mkfs tool, but a fuzzer.
Fix this by open coding xlog_logrec_hblks and taking the fixed h_size into account for this calculation.
From the CVE record · Linux
The Linux kernel’s XFS log recovery code can allocate a buffer using an incorrect log header size. A malformed h_size value, such as one supplied by a fuzzer, can cause an out-of-bounds access during recovery. The input does not specify whether exploitation requires local access, authentication, or user interaction.
Engineers running Linux systems that use XFS should check their kernel versions; affected versions are not specified.