btrfs: detach failed sprout device from transaction update list
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bbbf7243d62d8be73b7ef60721c127b36b2d523e · < 8b001df2b37ca022f710f3254fbb0bcd6d9e1bed| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
btrfs: detach failed sprout device from transaction update list
When creating the first metadata chunk for a sprout filesystem, create_chunk() adds the new device to the transaction dev_update_list through device->post_commit_list.
If the subsequent system chunk creation fails, btrfs_init_new_device() aborts the transaction and releases the device while post_commit_list is still linked. This triggers a warning in btrfs_free_device() and leaves the transaction list referencing freed memory.
Detach the device while holding chunk_mutex before releasing it.
From the CVE record · Linux
The Linux kernel’s btrfs code can leave a transaction list referencing a freed device when system chunk creation fails while initializing a sprout filesystem. This triggers a warning and creates a use-after-free risk. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with btrfs should check their kernel versions; affected versions are not specified.