btrfs: fix extent map use-after-free when handling missing device in read_one_chunk
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: fix extent map use-after-free when handling missing device in read_one_chunk
Store the error code before freeing the extent_map. Though it's reference counted structure, in that function it's the first and last allocation so this would lead to a potential use-after-free.
The error can happen eg. when chunk is stored on a missing device and the degraded mount option is missing.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=216721
From the CVE record · Linux
The Linux kernel’s btrfs read_one_chunk function can access a freed extent map when a chunk is on a missing device and the degraded mount option is absent. The input does not specify whether an attacker can trigger this condition or whether access or user interaction is required.
Administrators running Linux kernels with btrfs should check their systems; affected versions are not specified.