From: Greg KH <gregkh@linuxfoundation.org>
To: Shubham Pushpkar <spushpka@cisco.com>
Cc: stable@vger.kernel.org
Subject: Re: [Fix CVE-2024-50217 in v6.6.y] [PATCH] btrfs: fix use-after-free of block device file in __btrfs_free_extra_devids()
Date: Mon, 3 Feb 2025 12:29:17 +0100 [thread overview]
Message-ID: <2025020310-daydream-crop-4269@gregkh> (raw)
In-Reply-To: <20250203104254.4146544-1-spushpka@cisco.com>
On Mon, Feb 03, 2025 at 02:42:54AM -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
Nit, as we assign CVEs _after_ a commit happens, there's no need to add
this to a commit here as it is implied by the assignment database of
cves-to-commits.
Also, any specific reason you didn't cc: everyone involved in this
commit for your backport as well?
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-03 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 10:42 [Fix CVE-2024-50217 in v6.6.y] [PATCH] btrfs: fix use-after-free of block device file in __btrfs_free_extra_devids() Shubham Pushpkar
2025-02-03 11:29 ` Greg KH [this message]
[not found] ` <SA0PR11MB4701319AF5E422D47C4365C0D7F52@SA0PR11MB4701.namprd11.prod.outlook.com>
2025-02-03 14:07 ` Greg KH
[not found] ` <SA0PR11MB470126EB89552EDF95B010C8D7F52@SA0PR11MB4701.namprd11.prod.outlook.com>
2025-02-03 19:13 ` Greg KH
2025-02-03 16:24 ` Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2025-02-03 12:37 Shubham Pushpkar
2025-02-03 13:48 ` Harshit Mogalapalli
2025-02-03 16:24 ` Sasha Levin
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=2025020310-daydream-crop-4269@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=spushpka@cisco.com \
--cc=stable@vger.kernel.org \
/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