CVE-2023-52737

一、漏洞信息
 漏洞编号：[CVE-2023-52737](https://nvd.nist.gov/vuln/detail/CVE-2023-52737)
 漏洞归属组件：[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: lock the inode in shared mode before starting fiemapCurrently fiemap does not take the inode s lock (VFS lock), it only locksa file range in the inode s io tree. This however can lead to a deadlockif we have a concurrent fsync on the file and fiemap code triggers a faultwhen accessing the user space buffer with fiemap_fill_next_extent(). Thedeadlock happens on the inode s i_mmap_lock semaphore, which is taken bothby fsync and btrfs_page_mkwrite(). This deadlock was recently reported bysyzbot and triggers a trace like the following:   task:syz-executor361 state:D stack:20264 pid:5668  ppid:5119   flags:0x00004004   Call Trace:    <TASK>    context_switch kernel/sched/core.c:5293 [inline]    __schedule+0x995/0xe20 kernel/sched/core.c:6606    schedule+0xcb/0x190 kernel/sched/core.c:6682    wait_on_state fs/btrfs/extent-io-tree.c:707 [inline]    wait_extent_bit+0x577/0x6f0 fs/btrfs/extent-io-tree.c:751    lock_extent+0x1c2/0x280 fs/btrfs/extent-io-tree.c:1742    find_lock_delalloc_range+0x4e6/0x9c0 fs/btrfs/extent_io.c:488    writepage_delalloc+0x1ef/0x540 fs/btrfs/extent_io.c:1863    __extent_writepage+0x736/0x14e0 fs/btrfs/extent_io.c:2174    extent_write_cache_pages+0x983/0x1220 fs/btrfs/extent_io.c:3091    extent_writepages+0x219/0x540 fs/btrfs/extent_io.c:3211    do_writepages+0x3c3/0x680 mm/page-writeback.c:2581    filemap_fdatawrite_wbc+0x11e/0x170 mm/filemap.c:388    __filemap_fdatawrite_range mm/filemap.c:421 [inline]    filemap_fdatawrite_range+0x175/0x200 mm/filemap.c:439    btrfs_fdatawrite_range fs/btrfs/file.c:3850 [inline]    start_ordered_ops fs/btrfs/file.c:1737 [inline]    btrfs_sync_file+0x4ff/0x1190 fs/btrfs/file.c:1839    generic_write_sync include/linux/fs.h:2885 [inline]    btrfs_do_write_iter+0xcd3/0x1280 fs/btrfs/file.c:1684    call_write_iter include/linux/fs.h:2189 [inline]    new_sync_write fs/read_write.c:491 [inline]    vfs_write+0x7dc/0xc50 fs/read_write.c:584    ksys_write+0x177/0x2a0 fs/read_write.c:637    do_syscall_x64 arch/x86/entry/common.c:50 [inline]    do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80    entry_SYSCALL_64_after_hwframe+0x63/0xcd   RIP: 0033:0x7f7d4054e9b9   RSP: 002b:00007f7d404fa2f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001   RAX: ffffffffffffffda RBX: 00007f7d405d87a0 RCX: 00007f7d4054e9b9   RDX: 0000000000000090 RSI: 0000000020000000 RDI: 0000000000000006   RBP: 00007f7d405a51d0 R08: 0000000000000000 R09: 0000000000000000   R10: 0000000000000000 R11: 0000000000000246 R12: 61635f65646f6e69   R13: 65646f7475616f6e R14: 7261637369646f6e R15: 00007f7d405d87a8    </TASK>   INFO: task syz-executor361:5697 blocked for more than 145 seconds.         Not tainted 6.2.0-rc3-syzkaller-00376-g7c6984405241 #0    echo 0 > /proc/sys/kernel/hung_task_timeout_secs  disables this message.   task:syz-executor361 state:D stack:21216 pid:5697  ppid:5119   flags:0x00004004   Call Trace:    <TASK>    context_switch kernel/sched/core.c:5293 [inline]    __schedule+0x995/0xe20 kernel/sched/core.c:6606    schedule+0xcb/0x190 kernel/sched/core.c:6682    rwsem_down_read_slowpath+0x5f9/0x930 kernel/locking/rwsem.c:1095    __down_read_common+0x54/0x2a0 kernel/locking/rwsem.c:1260    btrfs_page_mkwrite+0x417/0xc80 fs/btrfs/inode.c:8526    do_page_mkwrite+0x19e/0x5e0 mm/memory.c:2947    wp_page_shared+0x15e/0x380 mm/memory.c:3295    handle_pte_fault mm/memory.c:4949 [inline]    __handle_mm_fault mm/memory.c:5073 [inline]    handle_mm_fault+0x1b79/0x26b0 mm/memory.c:5219    do_user_addr_fault+0x69b/0xcb0 arch/x86/mm/fault.c:1428    handle_page_fault arch/x86/mm/fault.c:1519 [inline]    exc_page_fault+0x7a/0x110 arch/x86/mm/fault.c:1575    asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570   RIP: 0010:copy_user_short_string+0xd/0x40 arch/x86/lib/copy_user_64.S:233   Code: 74 0a 89 (...)   RSP: 0018:ffffc9000570f330 EFLAGS: 000502---truncated---
 漏洞公开时间：2024-05-22 00:15:13
 漏洞创建时间：2024-05-21 18:44:55
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2023-52737
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/519b7e13b5ae8dd38da1e52275705343be6bb508 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/d8c594da79bc0244e610a70594e824a401802be1 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52737 | https://bugzilla.suse.com/show_bug.cgi?id=1225484 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2023/CVE-2023-52737.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1225484 |
| suse_bugzilla | https://git.kernel.org/stable/c/d8c594da79bc0244e610a70594e824a401802be1 | https://bugzilla.suse.com/show_bug.cgi?id=1225484 |
| suse_bugzilla | https://git.kernel.org/stable/c/519b7e13b5ae8dd38da1e52275705343be6bb508 | https://bugzilla.suse.com/show_bug.cgi?id=1225484 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2023-52737 | https://bugzilla.suse.com/show_bug.cgi?id=1225484 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024052101-CVE-2023-52737-e10e@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2282713 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2023-52737 | https://ubuntu.com/security/CVE-2023-52737 |
| ubuntu | https://git.kernel.org/linus/519b7e13b5ae8dd38da1e52275705343be6bb508 (6.2-rc8) | https://ubuntu.com/security/CVE-2023-52737 |
| ubuntu | https://git.kernel.org/stable/c/d8c594da79bc0244e610a70594e824a401802be1 | https://ubuntu.com/security/CVE-2023-52737 |
| ubuntu | https://git.kernel.org/stable/c/519b7e13b5ae8dd38da1e52275705343be6bb508 | https://ubuntu.com/security/CVE-2023-52737 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2023-52737 | https://ubuntu.com/security/CVE-2023-52737 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2023-52737 | https://ubuntu.com/security/CVE-2023-52737 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2023-52737 | https://ubuntu.com/security/CVE-2023-52737 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2023-52737 |
| anolis |  | https://anas.openanolis.cn/cves/detail/CVE-2023-52737 |

</details>

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

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux |  | https://git.kernel.org/linus/519b7e13b5ae8dd38da1e52275705343be6bb508 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:btrfs: lock the inode in shared mode before starting fiemapCurrently fiemap does not take the inode s lock (VFS lock), it only locksa file range in the inode s io tree. This however can lead to a deadlockif we have a concurrent fsync on the file and fiemap code triggers a faultwhen accessing the user space buffer with fiemap_fill_next_extent(). Thedeadlock happens on the inode s i_mmap_lock semaphore, which is taken bothby fsync and btrfs_page_mkwrite(). This deadlock was recently reported bysyzbot and triggers a trace like the following:   task:syz-executor361 state:D stack:20264 pid:5668  ppid:5119   flags:0x00004004   Call Trace:    <TASK>    context_switch kernel/sched/core.c:5293 [inline]    __schedule+0x995/0xe20 kernel/sched/core.c:6606    schedule+0xcb/0x190 kernel/sched/core.c:6682    wait_on_state fs/btrfs/extent-io-tree.c:707 [inline]    wait_extent_bit+0x577/0x6f0 fs/btrfs/extent-io-tree.c:751    lock_extent+0x1c2/0x280 fs/btrfs/extent-io-tree.c:1742    find_lock_delalloc_range+0x4e6/0x9c0 fs/btrfs/extent_io.c:488    writepage_delalloc+0x1ef/0x540 fs/btrfs/extent_io.c:1863    __extent_writepage+0x736/0x14e0 fs/btrfs/extent_io.c:2174    extent_write_cache_pages+0x983/0x1220 fs/btrfs/extent_io.c:3091    extent_writepages+0x219/0x540 fs/btrfs/extent_io.c:3211    do_writepages+0x3c3/0x680 mm/page-writeback.c:2581    filemap_fdatawrite_wbc+0x11e/0x170 mm/filemap.c:388    __filemap_fdatawrite_range mm/filemap.c:421 [inline]    filemap_fdatawrite_range+0x175/0x200 mm/filemap.c:439    btrfs_fdatawrite_range fs/btrfs/file.c:3850 [inline]    start_ordered_ops fs/btrfs/file.c:1737 [inline]    btrfs_sync_file+0x4ff/0x1190 fs/btrfs/file.c:1839    generic_write_sync include/linux/fs.h:2885 [inline]    btrfs_do_write_iter+0xcd3/0x1280 fs/btrfs/file.c:1684    call_write_iter include/linux/fs.h:2189 [inline]    new_sync_write fs/read_write.c:491 [inline]    vfs_write+0x7dc/0xc50 fs/read_write.c:584    ksys_write+0x177/0x2a0 fs/read_write.c:637    do_syscall_x64 arch/x86/entry/common.c:50 [inline]    do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80    entry_SYSCALL_64_after_hwframe+0x63/0xcd   RIP: 0033:0x7f7d4054e9b9   RSP: 002b:00007f7d404fa2f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001   RAX: ffffffffffffffda RBX: 00007f7d405d87a0 RCX: 00007f7d4054e9b9   RDX: 0000000000000090 RSI: 0000000020000000 RDI: 0000000000000006   RBP: 00007f7d405a51d0 R08: 0000000000000000 R09: 0000000000000000   R10: 0000000000000000 R11: 0000000000000246 R12: 61635f65646f6e69   R13: 65646f7475616f6e R14: 7261637369646f6e R15: 00007f7d405d87a8    </TASK>   INFO: task syz-executor361:5697 blocked for more than 145 seconds.         Not tainted 6.2.0-rc3-syzkaller-00376-g7c6984405241 #0    echo 0 > /proc/sys/kernel/hung_task_timeout_secs  disables this message.   task:syz-executor361 state:D stack:21216 pid:5697  ppid:5119   flags:0x00004004   Call Trace:    <TASK>    context_switch kernel/sched/core.c:5293 [inline]    __schedule+0x995/0xe20 kernel/sched/core.c:6606    schedule+0xcb/0x190 kernel/sched/core.c:6682    rwsem_down_read_slowpath+0x5f9/0x930 kernel/locking/rwsem.c:1095    __down_read_common+0x54/0x2a0 kernel/locking/rwsem.c:1260    btrfs_page_mkwrite+0x417/0xc80 fs/btrfs/inode.c:8526    do_page_mkwrite+0x19e/0x5e0 mm/memory.c:2947    wp_page_shared+0x15e/0x380 mm/memory.c:3295    handle_pte_fault mm/memory.c:4949 [inline]    __handle_mm_fault mm/memory.c:5073 [inline]    handle_mm_fault+0x1b79/0x26b0 mm/memory.c:5219    do_user_addr_fault+0x69b/0xcb0 arch/x86/mm/fault.c:1428    handle_page_fault arch/x86/mm/fault.c:1519 [inline]    exc_page_fault+0x7a/0x110 arch/x86/mm/fault.c:1575    asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570   RIP: 0010:copy_user_short_string+0xd/0x40 arch/x86/lib/copy_user_64.S:233   Code: 74 0a 89 (...)   RSP: 0018:ffffc9000570f330 EFLAGS: 000502---truncated---
 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-SP3(5.10.0):不受影响
3.openEuler-22.03-LTS-SP4(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-24.03-LTS-SP1(6.6.0):不受影响
8.openEuler-24.03-LTS-SP2(6.6.0):不受影响

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

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

src-openEuler/kernel
关闭

内容风险标识

评论 (20)

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

内容风险标识

CVE-2023-52737

评论 (20)

搜索帮助

src-openEuler/kernel
关闭