btrfs: zoned: fix use-after-free due to race with dev replace
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:
btrfs: zoned: fix use-after-free due to race with dev replace
While loading a zone's info during creation of a block group, we can race with a device replace operation and then trigger a use-after-free on the device that was just replaced (source device of the replace operation).
This happens because at btrfs_load_zone_info() we extract a device from the chunk map into a local variable and then use the device while not under the protection of the device replace rwsem. So if there's a device replace operation happening when we extract the device and that device is the source of the replace operation, we will trigger a use-after-free if before we finish using the device the replace operation finishes and frees the device.
Fix this by enlarging the critical section under the protection of the device replace rwsem so that all uses of the device are done inside the critical section.
From the CVE record · Linux
The Linux kernel’s btrfs zoned code can use a freed device while loading zone information during block-group creation. This can happen if a device replacement finishes while that device is in use; the input does not specify how an attacker could trigger the race, whether authentication is needed, or whether user interaction is required.
Engineers running Linux kernels with btrfs zoned support should check their kernel versions; affected versions are not specified.