Linux kernel cross-rtgroup extent reaping in XFS repair
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 |
|
|
6.18.617.3.27.4-rc1In the Linux kernel, the following vulnerability has been resolved:
xfs: avoid cross-rtgroup reaping after a repair
LOLLM notices that the extents stored in a xrtb_bitmap (aka xfs_rtblock bitmap) can span multiple rtgroups due to two circumstances. The first is that the size of an rtgroup is an exact power of two, which means that rtgroups are adjacent in the segmented xfs_rtblock_t address space. This is fairly common to reduce the amount of multiplication and division needed to handle space on the rt volume.
The second is that (unlike in the original rtgroups design), rtgroups do not have fixed-location metadata like AGs do, which means that there's nothing to force a break between rtgroups.
Therefore, we must loop through the rtgroups in xreap_rtmeta_extent to avoid running off the end of an rtgroup while reaping.
From the CVE record · Linux
The Linux kernel’s XFS repair code can reap an extent past the end of a realtime group when a realtime-block bitmap spans multiple groups. The input does not specify an attacker scenario, authentication requirements, or whether user interaction is needed.
Engineers running Linux kernels with XFS realtime-group support should check their affected versions; none are listed in the input.