From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Shubham Pushpkar <spushpka@cisco.com>, Sasha Levin <sashal@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 11:24:57 -0500 [thread overview]
Message-ID: <20250203104236-79c0781f6bba7d6e@stable.kernel.org> (raw)
In-Reply-To: <20250203123719.52811-1-spushpka@cisco.com>
[ Sasha's backport helper bot ]
Hi,
Found matching upstream commit: aec8e6bf839101784f3ef037dcdb9432c3f32343
WARNING: Author mismatch between patch and found commit:
Backport author: Shubham Pushpkar<spushpka@cisco.com>
Commit author: Zhihao Cheng<chengzhihao1@huawei.com>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: aec8e6bf83910 ! 1: afbc8c0c36536 btrfs: fix use-after-free of block device file in __btrfs_free_extra_devids()
@@ Metadata
## Commit message ##
btrfs: fix use-after-free of block device file in __btrfs_free_extra_devids()
+ 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
@@ Commit message
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 ##
@@ fs/btrfs/volumes.c: static void btrfs_close_one_device(struct btrfs_device *device)
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Failed |
Build Errors:
Build error for stable/linux-6.6.y:
lib/test_dhry.o: warning: objtool: dhry() falls through to next function dhry_run_set.cold()
fs/btrfs/volumes.c: In function 'btrfs_close_one_device':
fs/btrfs/volumes.c:1179:23: error: 'struct btrfs_device' has no member named 'bdev_file'
1179 | device->bdev_file = NULL;
| ^~
make[4]: *** [scripts/Makefile.build:243: fs/btrfs/volumes.o] Error 1
make[4]: Target 'fs/btrfs/' not remade because of errors.
make[3]: *** [scripts/Makefile.build:480: fs/btrfs] Error 2
make[3]: Target 'fs/' not remade because of errors.
make[2]: *** [scripts/Makefile.build:480: fs] Error 2
make[2]: Target './' not remade because of errors.
make[1]: *** [/home/sasha/build/linus-next/Makefile:1921: .] Error 2
make[1]: Target '__all' not remade because of errors.
make: *** [Makefile:234: __sub-make] Error 2
make: Target '__all' not remade because of errors.
next prev parent reply other threads:[~2025-02-03 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 12:37 [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 13:48 ` Harshit Mogalapalli
2025-02-03 16:24 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-03 10:42 Shubham Pushpkar
2025-02-03 11:29 ` Greg KH
[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
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=20250203104236-79c0781f6bba7d6e@stable.kernel.org \
--to=sashal@kernel.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