btrfs: fix double free in create_space_info_sub_group() error path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f92ee31e031c7819126d2febdda0c3e91f5d2eb9 · < a7449edf96143f192606ec8647e3167e1ecbd728| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix double free in create_space_info_sub_group() error path
When kobject_init_and_add() fails, the call chain is:
create_space_info_sub_group() -> btrfs_sysfs_add_space_info_type() -> kobject_init_and_add() -> failure -> kobject_put(&sub_group->kobj) -> space_info_release() -> kfree(sub_group)
Then control returns to create_space_info_sub_group(), where:
btrfs_sysfs_add_space_info_type() returns error -> kfree(sub_group)
Thus, sub_group is freed twice.
Keep parent->sub_group[index] = NULL for the failure path, but after btrfs_sysfs_add_space_info_type() has called kobject_put(), let the kobject release callback handle the cleanup.
From the CVE record · Linux
The Linux kernel’s btrfs code can free a space-info subgroup twice when kobject_init_and_add() fails. The input does not establish how an attacker could trigger this failure or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with btrfs should check whether their kernel includes the fix; affected versions are not specified.