From: "Daniel Walker (danielwa)" <danielwa@cisco.com>
To: "Shubham Pushpkar -X (spushpka - E INFOCHIPS PRIVATE LIMITED at
Cisco)" <spushpka@cisco.com>
Cc: "xe-linux-external(mailer list)" <xe-linux-external@cisco.com>,
Zhihao Cheng <chengzhihao1@huawei.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
David Sterba <dsterba@suse.com>
Subject: Re: [Internal Review] [Patch] btrfs: fix use-after-free of block device file in __btrfs_free_extra_devids()
Date: Thu, 23 Jan 2025 13:08:52 +0000 [thread overview]
Message-ID: <Z5I/YsJbzLaTBZ/9@goliath> (raw)
In-Reply-To: <20250123114141.1955806-1-spushpka@cisco.com>
Looks fine for release to me.
On Thu, Jan 23, 2025 at 03:41:41AM -0800, Shubham Pushpkar wrote:
> From: Zhihao Cheng <chengzhihao1@huawei.com>
>
> commit aec8e6bf839101784f3ef037dcdb9432c3f32343 ("btrfs:
> fix use-after-free of block device file in __btrfs_free_extra_devids()")
>
> Mounting btrfs from two images (which have the same one fsid and two
> different dev_uuids) in certain executing order may trigger an UAF for
> variable 'device->bdev_file' in __btrfs_free_extra_devids(). And
> following are the details:
>
> 1. Attach image_1 to loop0, attach image_2 to loop1, and scan btrfs
> devices by ioctl(BTRFS_IOC_SCAN_DEV):
>
> / btrfs_device_1 → loop0
> fs_device
> \ btrfs_device_2 → loop1
> 2. mount /dev/loop0 /mnt
> btrfs_open_devices
> btrfs_device_1->bdev_file = btrfs_get_bdev_and_sb(loop0)
> btrfs_device_2->bdev_file = btrfs_get_bdev_and_sb(loop1)
> btrfs_fill_super
> open_ctree
> fail: btrfs_close_devices // -ENOMEM
> btrfs_close_bdev(btrfs_device_1)
> fput(btrfs_device_1->bdev_file)
> // btrfs_device_1->bdev_file is freed
> btrfs_close_bdev(btrfs_device_2)
> fput(btrfs_device_2->bdev_file)
>
> 3. mount /dev/loop1 /mnt
> btrfs_open_devices
> btrfs_get_bdev_and_sb(&bdev_file)
> // EIO, btrfs_device_1->bdev_file is not assigned,
> // which points to a freed memory area
> btrfs_device_2->bdev_file = btrfs_get_bdev_and_sb(loop1)
> btrfs_fill_super
> open_ctree
> btrfs_free_extra_devids
> if (btrfs_device_1->bdev_file)
> fput(btrfs_device_1->bdev_file) // UAF !
>
> Fix it by setting 'device->bdev_file' as 'NULL' after closing the
> btrfs_device in btrfs_close_one_device().
>
> Fixes: CVE-2024-50217
> Fixes: 142388194191 ("btrfs: do not background blkdev_put()")
> CC: stable@vger.kernel.org # 4.19+
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=219408
> Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com>
> Reviewed-by: David Sterba <dsterba@suse.com>
> Signed-off-by: David Sterba <dsterba@suse.com>
> (cherry picked from commit aec8e6bf839101784f3ef037dcdb9432c3f32343)
> Signed-off-by: Shubham Pushpkar <spushpka@cisco.com>
> ---
> fs/btrfs/volumes.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index b9a0b26d08e1..ab2412542ce5 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -1176,6 +1176,7 @@ static void btrfs_close_one_device(struct btrfs_device *device)
> if (device->bdev) {
> fs_devices->open_devices--;
> device->bdev = NULL;
> + device->bdev_file = NULL;
> }
> clear_bit(BTRFS_DEV_STATE_WRITEABLE, &device->dev_state);
> btrfs_destroy_dev_zone_info(device);
> --
> 2.35.6
>
next prev parent reply other threads:[~2025-01-23 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 11:41 [Internal Review] [Patch] btrfs: fix use-after-free of block device file in __btrfs_free_extra_devids() Shubham Pushpkar
2025-01-23 13:08 ` Daniel Walker (danielwa) [this message]
2025-01-23 13:56 ` Greg KH
2025-01-23 14:20 ` Daniel Walker (danielwa)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z5I/YsJbzLaTBZ/9@goliath \
--to=danielwa@cisco.com \
--cc=chengzhihao1@huawei.com \
--cc=dsterba@suse.com \
--cc=spushpka@cisco.com \
--cc=stable@vger.kernel.org \
--cc=xe-linux-external@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox