CVE-2024-49869

一、漏洞信息
 漏洞编号：[CVE-2024-49869](https://nvd.nist.gov/vuln/detail/CVE-2024-49869)
 漏洞归属组件：[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：7.8 High
  Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:btrfs: send: fix buffer overflow detection when copying path to cache entryStarting with commit c0247d289e73 ( btrfs: send: annotate structname_cache_entry with __counted_by() ) we annotated the variable lengtharray  name  from the name_cache_entry structure with __counted_by() toimprove overflow detection. However that alone was not correct, becausethe length of that array does not match the  name_len  field - it matchesthat plus 1 to include the NUL string terminator, so that makes afortified kernel think there s an overflow and report a splat like this:  strcpy: detected buffer overflow: 20 byte write of buffer size 19  WARNING: CPU: 3 PID: 3310 at __fortify_report+0x45/0x50  CPU: 3 UID: 0 PID: 3310 Comm: btrfs Not tainted 6.11.0-prnet #1  Hardware name: CompuLab Ltd.  sbc-ihsw/Intense-PC2 (IPC2), BIOS IPC2_3.330.7 X64 03/15/2018  RIP: 0010:__fortify_report+0x45/0x50  Code: 48 8b 34 (...)  RSP: 0018:ffff97ebc0d6f650 EFLAGS: 00010246  RAX: 7749924ef60fa600 RBX: ffff8bf5446a521a RCX: 0000000000000027  RDX: 00000000ffffdfff RSI: ffff97ebc0d6f548 RDI: ffff8bf84e7a1cc8  RBP: ffff8bf548574080 R08: ffffffffa8c40e10 R09: 0000000000005ffd  R10: 0000000000000004 R11: ffffffffa8c70e10 R12: ffff8bf551eef400  R13: 0000000000000000 R14: 0000000000000013 R15: 00000000000003a8  FS:  00007fae144de8c0(0000) GS:ffff8bf84e780000(0000) knlGS:0000000000000000  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  CR2: 00007fae14691690 CR3: 00000001027a2003 CR4: 00000000001706f0  Call Trace:   <TASK>   ? __warn+0x12a/0x1d0   ? __fortify_report+0x45/0x50   ? report_bug+0x154/0x1c0   ? handle_bug+0x42/0x70   ? exc_invalid_op+0x1a/0x50   ? asm_exc_invalid_op+0x1a/0x20   ? __fortify_report+0x45/0x50   __fortify_panic+0x9/0x10  __get_cur_name_and_parent+0x3bc/0x3c0   get_cur_path+0x207/0x3b0   send_extent_data+0x709/0x10d0   ? find_parent_nodes+0x22df/0x25d0   ? mas_nomem+0x13/0x90   ? mtree_insert_range+0xa5/0x110   ? btrfs_lru_cache_store+0x5f/0x1e0   ? iterate_extent_inodes+0x52d/0x5a0   process_extent+0xa96/0x11a0   ? __pfx_lookup_backref_cache+0x10/0x10   ? __pfx_store_backref_cache+0x10/0x10   ? __pfx_iterate_backrefs+0x10/0x10   ? __pfx_check_extent_item+0x10/0x10   changed_cb+0x6fa/0x930   ? tree_advance+0x362/0x390   ? memcmp_extent_buffer+0xd7/0x160   send_subvol+0xf0a/0x1520   btrfs_ioctl_send+0x106b/0x11d0   ? __pfx___clone_root_cmp_sort+0x10/0x10   _btrfs_ioctl_send+0x1ac/0x240   btrfs_ioctl+0x75b/0x850   __se_sys_ioctl+0xca/0x150   do_syscall_64+0x85/0x160   ? __count_memcg_events+0x69/0x100   ? handle_mm_fault+0x1327/0x15c0   ? __se_sys_rt_sigprocmask+0xf1/0x180   ? syscall_exit_to_user_mode+0x75/0xa0   ? do_syscall_64+0x91/0x160   ? do_user_addr_fault+0x21d/0x630  entry_SYSCALL_64_after_hwframe+0x76/0x7e  RIP: 0033:0x7fae145eeb4f  Code: 00 48 89 (...)  RSP: 002b:00007ffdf1cb09b0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010  RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fae145eeb4f  RDX: 00007ffdf1cb0ad0 RSI: 0000000040489426 RDI: 0000000000000004  RBP: 00000000000078fe R08: 00007fae144006c0 R09: 00007ffdf1cb0927  R10: 0000000000000008 R11: 0000000000000246 R12: 00007ffdf1cb1ce8  R13: 0000000000000003 R14: 000055c499fab2e0 R15: 0000000000000004   </TASK>Fix this by not storing the NUL string terminator since we don t actuallyneed it for name cache entries, this way  name_len  corresponds to theactual size of the  name  array. This requires marking the  name  arrayfield with __nonstring and using memcpy() instead of strcpy() asrecommended by the guidelines at:   https://github.com/KSPP/linux/issues/90
 漏洞公开时间：2024-10-22 02:15:08
 漏洞创建时间：2024-10-22 04:25:55
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-49869
<details>
<summary>更多参考(点击展开)</summary>

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

</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/843738ede6cb8b959fb22591fcbabe8b456d7216 |  | nvd |
|  |  | https://git.kernel.org/stable/c/96c6ca71572a3556ed0c37237305657ff47174b7 |  | nvd |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:btrfs: send: fix buffer overflow detection when copying path to cache entryStarting with commit c0247d289e73 ( btrfs: send: annotate structname_cache_entry with __counted_by() ) we annotated the variable lengtharray  name  from the name_cache_entry structure with __counted_by() toimprove overflow detection. However that alone was not correct, becausethe length of that array does not match the  name_len  field - it matchesthat plus 1 to include the NUL string terminator, so that makes afortified kernel think there s an overflow and report a splat like this:  strcpy: detected buffer overflow: 20 byte write of buffer size 19  WARNING: CPU: 3 PID: 3310 at __fortify_report+0x45/0x50  CPU: 3 UID: 0 PID: 3310 Comm: btrfs Not tainted 6.11.0-prnet #1  Hardware name: CompuLab Ltd.  sbc-ihsw/Intense-PC2 (IPC2), BIOS IPC2_3.330.7 X64 03/15/2018  RIP: 0010:__fortify_report+0x45/0x50  Code: 48 8b 34 (...)  RSP: 0018:ffff97ebc0d6f650 EFLAGS: 00010246  RAX: 7749924ef60fa600 RBX: ffff8bf5446a521a RCX: 0000000000000027  RDX: 00000000ffffdfff RSI: ffff97ebc0d6f548 RDI: ffff8bf84e7a1cc8  RBP: ffff8bf548574080 R08: ffffffffa8c40e10 R09: 0000000000005ffd  R10: 0000000000000004 R11: ffffffffa8c70e10 R12: ffff8bf551eef400  R13: 0000000000000000 R14: 0000000000000013 R15: 00000000000003a8  FS:  00007fae144de8c0(0000) GS:ffff8bf84e780000(0000) knlGS:0000000000000000  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  CR2: 00007fae14691690 CR3: 00000001027a2003 CR4: 00000000001706f0  Call Trace:   <TASK>   ? __warn+0x12a/0x1d0   ? __fortify_report+0x45/0x50   ? report_bug+0x154/0x1c0   ? handle_bug+0x42/0x70   ? exc_invalid_op+0x1a/0x50   ? asm_exc_invalid_op+0x1a/0x20   ? __fortify_report+0x45/0x50   __fortify_panic+0x9/0x10  __get_cur_name_and_parent+0x3bc/0x3c0   get_cur_path+0x207/0x3b0   send_extent_data+0x709/0x10d0   ? find_parent_nodes+0x22df/0x25d0   ? mas_nomem+0x13/0x90   ? mtree_insert_range+0xa5/0x110   ? btrfs_lru_cache_store+0x5f/0x1e0   ? iterate_extent_inodes+0x52d/0x5a0   process_extent+0xa96/0x11a0   ? __pfx_lookup_backref_cache+0x10/0x10   ? __pfx_store_backref_cache+0x10/0x10   ? __pfx_iterate_backrefs+0x10/0x10   ? __pfx_check_extent_item+0x10/0x10   changed_cb+0x6fa/0x930   ? tree_advance+0x362/0x390   ? memcmp_extent_buffer+0xd7/0x160   send_subvol+0xf0a/0x1520   btrfs_ioctl_send+0x106b/0x11d0   ? __pfx___clone_root_cmp_sort+0x10/0x10   _btrfs_ioctl_send+0x1ac/0x240   btrfs_ioctl+0x75b/0x850   __se_sys_ioctl+0xca/0x150   do_syscall_64+0x85/0x160   ? __count_memcg_events+0x69/0x100   ? handle_mm_fault+0x1327/0x15c0   ? __se_sys_rt_sigprocmask+0xf1/0x180   ? syscall_exit_to_user_mode+0x75/0xa0   ? do_syscall_64+0x91/0x160   ? do_user_addr_fault+0x21d/0x630  entry_SYSCALL_64_after_hwframe+0x76/0x7e  RIP: 0033:0x7fae145eeb4f  Code: 00 48 89 (...)  RSP: 002b:00007ffdf1cb09b0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010  RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fae145eeb4f  RDX: 00007ffdf1cb0ad0 RSI: 0000000040489426 RDI: 0000000000000004  RBP: 00000000000078fe R08: 00007fae144006c0 R09: 00007ffdf1cb0927  R10: 0000000000000008 R11: 0000000000000246 R12: 00007ffdf1cb1ce8  R13: 0000000000000003 R14: 000055c499fab2e0 R15: 0000000000000004   </TASK>Fix this by not storing the NUL string terminator since we don t actuallyneed it for name cache entries, this way  name_len  corresponds to theactual size of the  name  array. This requires marking the  name  arrayfield with __nonstring and using memcpy() instead of strcpy() asrecommended by the guidelines at:   https://github.com/KSPP/linux/issues/90
 openEuler评分：
  7.8
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 (9)

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

Content Risk Flag

CVE-2024-49869

Comments (9)

Search

src-openEuler/kernel
Closed