CVE-2024-50118

一、漏洞信息
 漏洞编号：[CVE-2024-50118](https://nvd.nist.gov/vuln/detail/CVE-2024-50118)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0
 CVSS V3.0分值：
  BaseScore：5.5 Medium
  Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:btrfs: reject ro->rw reconfiguration if there are hard ro requirements[BUG]Syzbot reports the following crash:  BTRFS info (device loop0 state MCS): disabling free space tree  BTRFS info (device loop0 state MCS): clearing compat-ro feature flag for FREE_SPACE_TREE (0x1)  BTRFS info (device loop0 state MCS): clearing compat-ro feature flag for FREE_SPACE_TREE_VALID (0x2)  Oops: general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN NOPTI  KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014  RIP: 0010:backup_super_roots fs/btrfs/disk-io.c:1691 [inline]  RIP: 0010:write_all_supers+0x97a/0x40f0 fs/btrfs/disk-io.c:4041  Call Trace:   <TASK>   btrfs_commit_transaction+0x1eae/0x3740 fs/btrfs/transaction.c:2530   btrfs_delete_free_space_tree+0x383/0x730 fs/btrfs/free-space-tree.c:1312   btrfs_start_pre_rw_mount+0xf28/0x1300 fs/btrfs/disk-io.c:3012   btrfs_remount_rw fs/btrfs/super.c:1309 [inline]   btrfs_reconfigure+0xae6/0x2d40 fs/btrfs/super.c:1534   btrfs_reconfigure_for_mount fs/btrfs/super.c:2020 [inline]   btrfs_get_tree_subvol fs/btrfs/super.c:2079 [inline]   btrfs_get_tree+0x918/0x1920 fs/btrfs/super.c:2115   vfs_get_tree+0x90/0x2b0 fs/super.c:1800   do_new_mount+0x2be/0xb40 fs/namespace.c:3472   do_mount fs/namespace.c:3812 [inline]   __do_sys_mount fs/namespace.c:4020 [inline]   __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3997   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83   entry_SYSCALL_64_after_hwframe+0x77/0x7f[CAUSE]To support mounting different subvolume with different RO/RW flags forthe new mount APIs, btrfs introduced two workaround to support this feature:- Skip mount option/feature checks if we are mounting a different  subvolume- Reconfigure the fs to RW if the initial mount is ROCombining these two, we can have the following sequence:- Mount the fs ro,rescue=all,clear_cache,space_cache=v1  rescue=all will mark the fs as hard read-only, so no v2 cache clearing  will happen.- Mount a subvolume rw of the same fs.  We go into btrfs_get_tree_subvol(), but fc_mount() returns EBUSY  because our new fc is RW, different from the original fs.  Now we enter btrfs_reconfigure_for_mount(), which switches the RO flag  first so that we can grab the existing fs_info.  Then we reconfigure the fs to RW.- During reconfiguration, option/features check is skipped  This means we will restart the v2 cache clearing, and convert back to  v1 cache.  This will trigger fs writes, and since the original fs has  rescue=all   option, it skips the csum tree read.  And eventually causing NULL pointer dereference in super block  writeback.[FIX]For reconfiguration caused by different subvolume RO/RW flags, ensure wealways run btrfs_check_options() to ensure we have proper hard ROrequirements met.In fact the function btrfs_check_options() doesn t really do manycomplex checks, but hard RO requirement and some feature dependencychecks, thus there is no special reason not to do the check for mountreconfiguration.
 漏洞公开时间：2024-11-06 02:15:14
 漏洞创建时间：2024-11-06 02:35:08
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-50118
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/23724398b55d9570f6ae79dd2ea026fff8896bf1 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3c36a72c1d27de6618c1c480c793d9924640f5bb |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-50118 | https://bugzilla.suse.com/show_bug.cgi?id=1232859 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-50118 | https://bugzilla.suse.com/show_bug.cgi?id=1232859 |
| suse_bugzilla | https://git.kernel.org/stable/c/23724398b55d9570f6ae79dd2ea026fff8896bf1 | https://bugzilla.suse.com/show_bug.cgi?id=1232859 |
| suse_bugzilla | https://git.kernel.org/stable/c/3c36a72c1d27de6618c1c480c793d9924640f5bb | https://bugzilla.suse.com/show_bug.cgi?id=1232859 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-50118.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1232859 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2323936 | https://bugzilla.suse.com/show_bug.cgi?id=1232859 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-50118 |

</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  openBrain开源漏洞感知系统
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
|  |  | https://git.kernel.org/stable/c/23724398b55d9570f6ae79dd2ea026fff8896bf1 |  | nvd |
|  |  | https://git.kernel.org/stable/c/3c36a72c1d27de6618c1c480c793d9924640f5bb |  | nvd |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:btrfs: reject ro->rw reconfiguration if there are hard ro requirements[BUG]Syzbot reports the following crash:  BTRFS info (device loop0 state MCS): disabling free space tree  BTRFS info (device loop0 state MCS): clearing compat-ro feature flag for FREE_SPACE_TREE (0x1)  BTRFS info (device loop0 state MCS): clearing compat-ro feature flag for FREE_SPACE_TREE_VALID (0x2)  Oops: general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN NOPTI  KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014  RIP: 0010:backup_super_roots fs/btrfs/disk-io.c:1691 [inline]  RIP: 0010:write_all_supers+0x97a/0x40f0 fs/btrfs/disk-io.c:4041  Call Trace:   <TASK>   btrfs_commit_transaction+0x1eae/0x3740 fs/btrfs/transaction.c:2530   btrfs_delete_free_space_tree+0x383/0x730 fs/btrfs/free-space-tree.c:1312   btrfs_start_pre_rw_mount+0xf28/0x1300 fs/btrfs/disk-io.c:3012   btrfs_remount_rw fs/btrfs/super.c:1309 [inline]   btrfs_reconfigure+0xae6/0x2d40 fs/btrfs/super.c:1534   btrfs_reconfigure_for_mount fs/btrfs/super.c:2020 [inline]   btrfs_get_tree_subvol fs/btrfs/super.c:2079 [inline]   btrfs_get_tree+0x918/0x1920 fs/btrfs/super.c:2115   vfs_get_tree+0x90/0x2b0 fs/super.c:1800   do_new_mount+0x2be/0xb40 fs/namespace.c:3472   do_mount fs/namespace.c:3812 [inline]   __do_sys_mount fs/namespace.c:4020 [inline]   __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3997   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83   entry_SYSCALL_64_after_hwframe+0x77/0x7f[CAUSE]To support mounting different subvolume with different RO/RW flags forthe new mount APIs, btrfs introduced two workaround to support this feature:- Skip mount option/feature checks if we are mounting a different  subvolume- Reconfigure the fs to RW if the initial mount is ROCombining these two, we can have the following sequence:- Mount the fs ro,rescue=all,clear_cache,space_cache=v1  rescue=all will mark the fs as hard read-only, so no v2 cache clearing  will happen.- Mount a subvolume rw of the same fs.  We go into btrfs_get_tree_subvol(), but fc_mount() returns EBUSY  because our new fc is RW, different from the original fs.  Now we enter btrfs_reconfigure_for_mount(), which switches the RO flag  first so that we can grab the existing fs_info.  Then we reconfigure the fs to RW.- During reconfiguration, option/features check is skipped  This means we will restart the v2 cache clearing, and convert back to  v1 cache.  This will trigger fs writes, and since the original fs has  rescue=all   option, it skips the csum tree read.  And eventually causing NULL pointer dereference in super block  writeback.[FIX]For reconfiguration caused by different subvolume RO/RW flags, ensure wealways run btrfs_check_options() to ensure we have proper hard ROrequirements met.In fact the function btrfs_check_options() doesn t really do manycomplex checks, but hard RO requirement and some feature dependencychecks, thus there is no special reason not to do the check for mountreconfiguration.
 openEuler评分：
  5.5
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
  1.openEuler-20.03-LTS-SP4(4.19.90):不受影响
2.openEuler-22.03-LTS-SP1(5.10.0):不受影响
3.openEuler-22.03-LTS-SP3(5.10.0):不受影响
4.openEuler-22.03-LTS-SP4(5.10.0):不受影响
5.master(6.6.0):不受影响
6.openEuler-24.03-LTS(6.6.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响
8.openEuler-24.03-LTS-SP1(6.6.0):不受影响

修复是否涉及abi变化(是/否)：
  1.openEuler-20.03-LTS-SP4(4.19.90):否
2.openEuler-22.03-LTS-SP1(5.10.0):否
3.openEuler-22.03-LTS-SP3(5.10.0):否
4.master(6.6.0):否
5.openEuler-24.03-LTS(6.6.0):否
6.openEuler-24.03-LTS-Next(6.6.0):否
7.openEuler-22.03-LTS-SP4(5.10.0):否
8.openEuler-24.03-LTS-SP1(6.6.0):否

原因说明：
  1.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在
2.openEuler-22.03-LTS-SP1(5.10.0):不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在
4.openEuler-22.03-LTS-SP4(5.10.0):不受影响-漏洞代码不存在
5.master(6.6.0):不受影响-漏洞代码不存在
6.openEuler-24.03-LTS(6.6.0):不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不存在
8.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不存在

src-openEuler/kernel
Closed

Content Risk Flag

Comments (10)

src-openEuler/kernelClosed .gitee-modal { width: 500px !important; }

Content Risk Flag

CVE-2024-50118

Comments (10)

Search

src-openEuler/kernel
Closed