CVE-2022-49007

一、漏洞信息
 漏洞编号：[CVE-2022-49007](https://nvd.nist.gov/vuln/detail/CVE-2022-49007)
 漏洞归属组件：[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:nilfs2: fix NULL pointer dereference in nilfs_palloc_commit_free_entry()Syzbot reported a null-ptr-deref bug: NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] CPU: 1 PID: 3603 Comm: segctord Not tainted 6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022 RIP: 0010:nilfs_palloc_commit_free_entry+0xe5/0x6b0 fs/nilfs2/alloc.c:608 Code: 00 00 00 00 fc ff df 80 3c 02 00 0f 85 cd 05 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 73 08 49 8d 7e 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 26 05 00 00 49 8b 46 10 be a6 00 00 00 48 c7 c7 RSP: 0018:ffffc90003dff830 EFLAGS: 00010212 RAX: dffffc0000000000 RBX: ffff88802594e218 RCX: 000000000000000d RDX: 0000000000000002 RSI: 0000000000002000 RDI: 0000000000000010 RBP: ffff888071880222 R08: 0000000000000005 R09: 000000000000003f R10: 000000000000000d R11: 0000000000000000 R12: ffff888071880158 R13: ffff88802594e220 R14: 0000000000000000 R15: 0000000000000004 FS:  0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fb1c08316a8 CR3: 0000000018560000 CR4: 0000000000350ee0 Call Trace:  <TASK>  nilfs_dat_commit_free fs/nilfs2/dat.c:114 [inline]  nilfs_dat_commit_end+0x464/0x5f0 fs/nilfs2/dat.c:193  nilfs_dat_commit_update+0x26/0x40 fs/nilfs2/dat.c:236  nilfs_btree_commit_update_v+0x87/0x4a0 fs/nilfs2/btree.c:1940  nilfs_btree_commit_propagate_v fs/nilfs2/btree.c:2016 [inline]  nilfs_btree_propagate_v fs/nilfs2/btree.c:2046 [inline]  nilfs_btree_propagate+0xa00/0xd60 fs/nilfs2/btree.c:2088  nilfs_bmap_propagate+0x73/0x170 fs/nilfs2/bmap.c:337  nilfs_collect_file_data+0x45/0xd0 fs/nilfs2/segment.c:568  nilfs_segctor_apply_buffers+0x14a/0x470 fs/nilfs2/segment.c:1018  nilfs_segctor_scan_file+0x3f4/0x6f0 fs/nilfs2/segment.c:1067  nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1197 [inline]  nilfs_segctor_collect fs/nilfs2/segment.c:1503 [inline]  nilfs_segctor_do_construct+0x12fc/0x6af0 fs/nilfs2/segment.c:2045  nilfs_segctor_construct+0x8e3/0xb30 fs/nilfs2/segment.c:2379  nilfs_segctor_thread_construct fs/nilfs2/segment.c:2487 [inline]  nilfs_segctor_thread+0x3c3/0xf30 fs/nilfs2/segment.c:2570  kthread+0x2e4/0x3a0 kernel/kthread.c:376  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306  </TASK> ...If DAT metadata file is corrupted on disk, there is a case wherereq->pr_desc_bh is NULL and blocknr is 0 at nilfs_dat_commit_end() duringa b-tree operation that cascadingly updates ancestor nodes of the b-tree,because nilfs_dat_commit_alloc() for a lower level block can initializethe blocknr on the same DAT entry between nilfs_dat_prepare_end() andnilfs_dat_commit_end().If this happens, nilfs_dat_commit_end() calls nilfs_dat_commit_free()without valid buffer heads in req->pr_desc_bh and req->pr_bitmap_bh, andcauses the NULL pointer dereference above innilfs_palloc_commit_free_entry() function, which leads to a crash.Fix this by adding a NULL check on req->pr_desc_bh and req->pr_bitmap_bhbefore nilfs_palloc_commit_free_entry() in nilfs_dat_commit_free().This also calls nilfs_error() in that case to notify that there is a fatalflaw in the filesystem metadata and prevent further operations.
 漏洞公开时间：2024-10-22 04:15:12
 漏洞创建时间：2024-10-22 05:03:37
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2022-49007
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/165c7a3b27a3857ebf57f626b9f38b48b6792e68 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2f2c59506ae39496588ceb8b88bdbdbaed895d63 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/33021419fd81efd3d729a7f19341ba4b98fe66ce |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/381b84f60e549ea98cec4666c6c728b1b3318756 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/9a130b72e6bd1fb07fc3cde839dc6fb53da76f07 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/bc3fd3293887b4cf84a9109700faeb82de533c89 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/e858917ab785afe83c14f5ac141301216ccda847 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/f0a0ccda18d6fd826d7c7e7ad48a6ed61c20f8b4 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-49007 | https://bugzilla.suse.com/show_bug.cgi?id=1232170 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2022-49007 | https://bugzilla.suse.com/show_bug.cgi?id=1232170 |
| suse_bugzilla | https://git.kernel.org/stable/c/165c7a3b27a3857ebf57f626b9f38b48b6792e68 | https://bugzilla.suse.com/show_bug.cgi?id=1232170 |
| suse_bugzilla | https://git.kernel.org/stable/c/2f2c59506ae39496588ceb8b88bdbdbaed895d63 | https://bugzilla.suse.com/show_bug.cgi?id=1232170 |
| suse_bugzilla | https://git.kernel.org/stable/c/33021419fd81efd3d729a7f19341ba4b98fe66ce | https://bugzilla.suse.com/show_bug.cgi?id=1232170 |
| suse_bugzilla | https://git.kernel.org/stable/c/381b84f60e549ea98cec4666c6c728b1b3318756 | https://bugzilla.suse.com/show_bug.cgi?id=1232170 |
| suse_bugzilla | https://git.kernel.org/stable/c/9a130b72e6bd1fb07fc3cde839dc6fb53da76f07 | https://bugzilla.suse.com/show_bug.cgi?id=1232170 |
| suse_bugzilla | https://git.kernel.org/stable/c/bc3fd3293887b4cf84a9109700faeb82de533c89 | https://bugzilla.suse.com/show_bug.cgi?id=1232170 |
| suse_bugzilla | https://git.kernel.org/stable/c/e858917ab785afe83c14f5ac141301216ccda847 | https://bugzilla.suse.com/show_bug.cgi?id=1232170 |
| suse_bugzilla | https://git.kernel.org/stable/c/f0a0ccda18d6fd826d7c7e7ad48a6ed61c20f8b4 | https://bugzilla.suse.com/show_bug.cgi?id=1232170 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2022/CVE-2022-49007.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1232170 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2320740 | https://bugzilla.suse.com/show_bug.cgi?id=1232170 |

</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/165c7a3b27a3857ebf57f626b9f38b48b6792e68 |  | nvd |
|  |  | https://git.kernel.org/stable/c/2f2c59506ae39496588ceb8b88bdbdbaed895d63 |  | nvd |
|  |  | https://git.kernel.org/stable/c/33021419fd81efd3d729a7f19341ba4b98fe66ce |  | nvd |
|  |  | https://git.kernel.org/stable/c/381b84f60e549ea98cec4666c6c728b1b3318756 |  | nvd |
|  |  | https://git.kernel.org/stable/c/9a130b72e6bd1fb07fc3cde839dc6fb53da76f07 |  | nvd |
|  |  | https://git.kernel.org/stable/c/bc3fd3293887b4cf84a9109700faeb82de533c89 |  | nvd |
|  |  | https://git.kernel.org/stable/c/e858917ab785afe83c14f5ac141301216ccda847 |  | nvd |
|  |  | https://git.kernel.org/stable/c/f0a0ccda18d6fd826d7c7e7ad48a6ed61c20f8b4 |  | nvd |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:nilfs2: fix NULL pointer dereference in nilfs_palloc_commit_free_entry()Syzbot reported a null-ptr-deref bug: NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] CPU: 1 PID: 3603 Comm: segctord Not tainted 6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022 RIP: 0010:nilfs_palloc_commit_free_entry+0xe5/0x6b0 fs/nilfs2/alloc.c:608 Code: 00 00 00 00 fc ff df 80 3c 02 00 0f 85 cd 05 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 73 08 49 8d 7e 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 26 05 00 00 49 8b 46 10 be a6 00 00 00 48 c7 c7 RSP: 0018:ffffc90003dff830 EFLAGS: 00010212 RAX: dffffc0000000000 RBX: ffff88802594e218 RCX: 000000000000000d RDX: 0000000000000002 RSI: 0000000000002000 RDI: 0000000000000010 RBP: ffff888071880222 R08: 0000000000000005 R09: 000000000000003f R10: 000000000000000d R11: 0000000000000000 R12: ffff888071880158 R13: ffff88802594e220 R14: 0000000000000000 R15: 0000000000000004 FS:  0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fb1c08316a8 CR3: 0000000018560000 CR4: 0000000000350ee0 Call Trace:  <TASK>  nilfs_dat_commit_free fs/nilfs2/dat.c:114 [inline]  nilfs_dat_commit_end+0x464/0x5f0 fs/nilfs2/dat.c:193  nilfs_dat_commit_update+0x26/0x40 fs/nilfs2/dat.c:236  nilfs_btree_commit_update_v+0x87/0x4a0 fs/nilfs2/btree.c:1940  nilfs_btree_commit_propagate_v fs/nilfs2/btree.c:2016 [inline]  nilfs_btree_propagate_v fs/nilfs2/btree.c:2046 [inline]  nilfs_btree_propagate+0xa00/0xd60 fs/nilfs2/btree.c:2088  nilfs_bmap_propagate+0x73/0x170 fs/nilfs2/bmap.c:337  nilfs_collect_file_data+0x45/0xd0 fs/nilfs2/segment.c:568  nilfs_segctor_apply_buffers+0x14a/0x470 fs/nilfs2/segment.c:1018  nilfs_segctor_scan_file+0x3f4/0x6f0 fs/nilfs2/segment.c:1067  nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1197 [inline]  nilfs_segctor_collect fs/nilfs2/segment.c:1503 [inline]  nilfs_segctor_do_construct+0x12fc/0x6af0 fs/nilfs2/segment.c:2045  nilfs_segctor_construct+0x8e3/0xb30 fs/nilfs2/segment.c:2379  nilfs_segctor_thread_construct fs/nilfs2/segment.c:2487 [inline]  nilfs_segctor_thread+0x3c3/0xf30 fs/nilfs2/segment.c:2570  kthread+0x2e4/0x3a0 kernel/kthread.c:376  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306  </TASK> ...If DAT metadata file is corrupted on disk, there is a case wherereq->pr_desc_bh is NULL and blocknr is 0 at nilfs_dat_commit_end() duringa b-tree operation that cascadingly updates ancestor nodes of the b-tree,because nilfs_dat_commit_alloc() for a lower level block can initializethe blocknr on the same DAT entry between nilfs_dat_prepare_end() andnilfs_dat_commit_end().If this happens, nilfs_dat_commit_end() calls nilfs_dat_commit_free()without valid buffer heads in req->pr_desc_bh and req->pr_bitmap_bh, andcauses the NULL pointer dereference above innilfs_palloc_commit_free_entry() function, which leads to a crash.Fix this by adding a NULL check on req->pr_desc_bh and req->pr_bitmap_bhbefore nilfs_palloc_commit_free_entry() in nilfs_dat_commit_free().This also calls nilfs_error() in that case to notify that there is a fatalflaw in the filesystem metadata and prevent further operations.
 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):不受影响

修复是否涉及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):否

原因说明：
  1.master(6.6.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP1(5.10.0):
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-Next(6.6.0):

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2024-2324

src-openEuler / kernel
Closed

Content Risk Flag

Comments (7)

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

Content Risk Flag

CVE-2022-49007

Comments (7)

Search

src-openEuler / kernel
Closed