CVE-2021-47230

一、漏洞信息
 漏洞编号：[CVE-2021-47230](https://nvd.nist.gov/vuln/detail/CVE-2021-47230)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.1.8,6.4.0,6.6.0
 CVSS V3.0分值：
  BaseScore：6.6 Medium
  Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:KVM: x86: Immediately reset the MMU context when the SMM flag is clearedImmediately reset the MMU context when the vCPU s SMM flag is cleared sothat the SMM flag in the MMU role is always synchronized with the vCPU sflag.  If RSM fails (which isn t correctly emulated), KVM will bailwithout calling post_leave_smm() and leave the MMU in a bad state.The bad MMU role can lead to a NULL pointer dereference when grabbing ashadow page s rmap for a page fault as the initial lookups for the gfnwill happen with the vCPU s SMM flag (=0), whereas the rmap lookup willuse the shadow page s SMM flag, which comes from the MMU (=1).  SMM hasan entirely different set of memslots, and so the initial lookup can finda memslot (SMM=0) and then explode on the rmap memslot lookup (SMM=1).  general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN  KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]  CPU: 1 PID: 8410 Comm: syz-executor382 Not tainted 5.13.0-rc5-syzkaller #0  Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011  RIP: 0010:__gfn_to_rmap arch/x86/kvm/mmu/mmu.c:935 [inline]  RIP: 0010:gfn_to_rmap+0x2b0/0x4d0 arch/x86/kvm/mmu/mmu.c:947  Code: <42> 80 3c 20 00 74 08 4c 89 ff e8 f1 79 a9 00 4c 89 fb 4d 8b 37 44  RSP: 0018:ffffc90000ffef98 EFLAGS: 00010246  RAX: 0000000000000000 RBX: ffff888015b9f414 RCX: ffff888019669c40  RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001  RBP: 0000000000000001 R08: ffffffff811d9cdb R09: ffffed10065a6002  R10: ffffed10065a6002 R11: 0000000000000000 R12: dffffc0000000000  R13: 0000000000000003 R14: 0000000000000001 R15: 0000000000000000  FS:  000000000124b300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  CR2: 0000000000000000 CR3: 0000000028e31000 CR4: 00000000001526e0  DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  Call Trace:   rmap_add arch/x86/kvm/mmu/mmu.c:965 [inline]   mmu_set_spte+0x862/0xe60 arch/x86/kvm/mmu/mmu.c:2604   __direct_map arch/x86/kvm/mmu/mmu.c:2862 [inline]   direct_page_fault+0x1f74/0x2b70 arch/x86/kvm/mmu/mmu.c:3769   kvm_mmu_do_page_fault arch/x86/kvm/mmu.h:124 [inline]   kvm_mmu_page_fault+0x199/0x1440 arch/x86/kvm/mmu/mmu.c:5065   vmx_handle_exit+0x26/0x160 arch/x86/kvm/vmx/vmx.c:6122   vcpu_enter_guest+0x3bdd/0x9630 arch/x86/kvm/x86.c:9428   vcpu_run+0x416/0xc20 arch/x86/kvm/x86.c:9494   kvm_arch_vcpu_ioctl_run+0x4e8/0xa40 arch/x86/kvm/x86.c:9722   kvm_vcpu_ioctl+0x70f/0xbb0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3460   vfs_ioctl fs/ioctl.c:51 [inline]   __do_sys_ioctl fs/ioctl.c:1069 [inline]   __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:1055   do_syscall_64+0x3f/0xb0 arch/x86/entry/common.c:47   entry_SYSCALL_64_after_hwframe+0x44/0xae  RIP: 0033:0x440ce9
 漏洞公开时间：2024-05-21 23:15:12
 漏洞创建时间：2024-05-21 16:24:53
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2021-47230
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/669a8866e468fd020d34eb00e08cb41d3774b71b |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/78fcb2c91adfec8ce3a2ba6b4d0dda89f2f4a7c6 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/cbb425f62df9df7abee4b3f068f7ed6ffc3561e2 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/df9a40cfb3be2cbeb1c17bb67c59251ba16630f3 |  |
| af854a3a-2127-422b-91ae-364da2661108 | https://git.kernel.org/stable/c/669a8866e468fd020d34eb00e08cb41d3774b71b |  |
| af854a3a-2127-422b-91ae-364da2661108 | https://git.kernel.org/stable/c/78fcb2c91adfec8ce3a2ba6b4d0dda89f2f4a7c6 |  |
| af854a3a-2127-422b-91ae-364da2661108 | https://git.kernel.org/stable/c/cbb425f62df9df7abee4b3f068f7ed6ffc3561e2 |  |
| af854a3a-2127-422b-91ae-364da2661108 | https://git.kernel.org/stable/c/df9a40cfb3be2cbeb1c17bb67c59251ba16630f3 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-47230 | https://bugzilla.suse.com/show_bug.cgi?id=1224853 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2021-47230 | https://bugzilla.suse.com/show_bug.cgi?id=1224853 |
| suse_bugzilla | https://git.kernel.org/stable/c/669a8866e468fd020d34eb00e08cb41d3774b71b | https://bugzilla.suse.com/show_bug.cgi?id=1224853 |
| suse_bugzilla | https://git.kernel.org/stable/c/78fcb2c91adfec8ce3a2ba6b4d0dda89f2f4a7c6 | https://bugzilla.suse.com/show_bug.cgi?id=1224853 |
| suse_bugzilla | https://git.kernel.org/stable/c/cbb425f62df9df7abee4b3f068f7ed6ffc3561e2 | https://bugzilla.suse.com/show_bug.cgi?id=1224853 |
| suse_bugzilla | https://git.kernel.org/stable/c/df9a40cfb3be2cbeb1c17bb67c59251ba16630f3 | https://bugzilla.suse.com/show_bug.cgi?id=1224853 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2021/CVE-2021-47230.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1224853 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024052138-CVE-2021-47230-e1ff@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2282587 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2021-47230 | https://ubuntu.com/security/CVE-2021-47230 |
| ubuntu | https://git.kernel.org/linus/78fcb2c91adfec8ce3a2ba6b4d0dda89f2f4a7c6 (5.13-rc7) | https://ubuntu.com/security/CVE-2021-47230 |
| ubuntu | https://git.kernel.org/stable/c/cbb425f62df9df7abee4b3f068f7ed6ffc3561e2 | https://ubuntu.com/security/CVE-2021-47230 |
| ubuntu | https://git.kernel.org/stable/c/669a8866e468fd020d34eb00e08cb41d3774b71b | https://ubuntu.com/security/CVE-2021-47230 |
| ubuntu | https://git.kernel.org/stable/c/df9a40cfb3be2cbeb1c17bb67c59251ba16630f3 | https://ubuntu.com/security/CVE-2021-47230 |
| ubuntu | https://git.kernel.org/stable/c/78fcb2c91adfec8ce3a2ba6b4d0dda89f2f4a7c6 | https://ubuntu.com/security/CVE-2021-47230 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2021-47230 | https://ubuntu.com/security/CVE-2021-47230 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2021-47230 | https://ubuntu.com/security/CVE-2021-47230 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2021-47230 | https://ubuntu.com/security/CVE-2021-47230 |

</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/669a8866e468fd020d34eb00e08cb41d3774b71b |  | nvd |
|  |  | https://git.kernel.org/stable/c/78fcb2c91adfec8ce3a2ba6b4d0dda89f2f4a7c6 |  | nvd |
|  |  | https://git.kernel.org/stable/c/cbb425f62df9df7abee4b3f068f7ed6ffc3561e2 |  | nvd |
|  |  | https://git.kernel.org/stable/c/df9a40cfb3be2cbeb1c17bb67c59251ba16630f3 |  | nvd |
| linux |  | https://git.kernel.org/linus/78fcb2c91adfec8ce3a2ba6b4d0dda89f2f4a7c6 | https://git.kernel.org/linus/9ec19493fb86d6d5fbf9286b94ff21e56ef66376 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
                                In the Linux kernel, the following vulnerability has been resolved:KVM: x86: Immediately reset the MMU context when the SMM flag is clearedImmediately reset the MMU context when the vCPU s SMM flag is cleared sothat the SMM flag in the MMU role is always synchronized with the vCPU sflag.  If RSM fails (which isn t correctly emulated), KVM will bailwithout calling post_leave_smm() and leave the MMU in a bad state.The bad MMU role can lead to a NULL pointer dereference when grabbing ashadow page s rmap for a page fault as the initial lookups for the gfnwill happen with the vCPU s SMM flag (=0), whereas the rmap lookup willuse the shadow page s SMM flag, which comes from the MMU (=1).  SMM hasan entirely different set of memslots, and so the initial lookup can finda memslot (SMM=0) and then explode on the rmap memslot lookup (SMM=1).  general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN  KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]  CPU: 1 PID: 8410 Comm: syz-executor382 Not tainted 5.13.0-rc5-syzkaller #0  Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011  RIP: 0010:__gfn_to_rmap arch/x86/kvm/mmu/mmu.c:935 [inline]  RIP: 0010:gfn_to_rmap+0x2b0/0x4d0 arch/x86/kvm/mmu/mmu.c:947  Code: <42> 80 3c 20 00 74 08 4c 89 ff e8 f1 79 a9 00 4c 89 fb 4d 8b 37 44  RSP: 0018:ffffc90000ffef98 EFLAGS: 00010246  RAX: 0000000000000000 RBX: ffff888015b9f414 RCX: ffff888019669c40  RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001  RBP: 0000000000000001 R08: ffffffff811d9cdb R09: ffffed10065a6002  R10: ffffed10065a6002 R11: 0000000000000000 R12: dffffc0000000000  R13: 0000000000000003 R14: 0000000000000001 R15: 0000000000000000  FS:  000000000124b300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  CR2: 0000000000000000 CR3: 0000000028e31000 CR4: 00000000001526e0  DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  Call Trace:   rmap_add arch/x86/kvm/mmu/mmu.c:965 [inline]   mmu_set_spte+0x862/0xe60 arch/x86/kvm/mmu/mmu.c:2604   __direct_map arch/x86/kvm/mmu/mmu.c:2862 [inline]   direct_page_fault+0x1f74/0x2b70 arch/x86/kvm/mmu/mmu.c:3769   kvm_mmu_do_page_fault arch/x86/kvm/mmu.h:124 [inline]   kvm_mmu_page_fault+0x199/0x1440 arch/x86/kvm/mmu/mmu.c:5065   vmx_handle_exit+0x26/0x160 arch/x86/kvm/vmx/vmx.c:6122   vcpu_enter_guest+0x3bdd/0x9630 arch/x86/kvm/x86.c:9428   vcpu_run+0x416/0xc20 arch/x86/kvm/x86.c:9494   kvm_arch_vcpu_ioctl_run+0x4e8/0xa40 arch/x86/kvm/x86.c:9722   kvm_vcpu_ioctl+0x70f/0xbb0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3460   vfs_ioctl fs/ioctl.c:51 [inline]   __do_sys_ioctl fs/ioctl.c:1069 [inline]   __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:1055   do_syscall_64+0x3f/0xb0 arch/x86/entry/common.c:47   entry_SYSCALL_64_after_hwframe+0x44/0xae  RIP: 0033:0x440ce9               
 openEuler评分：
  6.6
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/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.12.33):不受影响
6.openEuler-24.03-LTS:不受影响
7.openEuler-24.03-LTS-Next:不受影响
8.openEuler-24.03-LTS-SP2:

修复是否涉及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.12.33):否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-22.03-LTS-SP4(5.10.0):否
8.openEuler-24.03-LTS-SP2:
9.master(6.12.33):
10.openEuler-20.03-LTS-SP4(4.19.90):
11.openEuler-22.03-LTS-SP3(5.10.0):
12.openEuler-22.03-LTS-SP4(5.10.0):
13.openEuler-24.03-LTS:
14.openEuler-24.03-LTS-Next:
15.openEuler-24.03-LTS-SP1:
16.openEuler-24.03-LTS-SP2:
17.master(6.12.33):
18.openEuler-20.03-LTS-SP4(4.19.90):
19.openEuler-22.03-LTS-SP3(5.10.0):
20.openEuler-22.03-LTS-SP4(5.10.0):
21.openEuler-24.03-LTS:
22.openEuler-24.03-LTS-Next:
23.openEuler-24.03-LTS-SP1:
24.openEuler-24.03-LTS-SP2:
25.master(6.12.33):
26.openEuler-20.03-LTS-SP4(4.19.90):
27.openEuler-22.03-LTS-SP3(5.10.0):
28.openEuler-22.03-LTS-SP4(5.10.0):
29.openEuler-24.03-LTS:
30.openEuler-24.03-LTS-Next:
31.openEuler-24.03-LTS-SP1:
32.openEuler-24.03-LTS-SP2:
33.master(6.12.33):
34.openEuler-20.03-LTS-SP4(4.19.90):
35.openEuler-22.03-LTS-SP3(5.10.0):
36.openEuler-22.03-LTS-SP4(5.10.0):
37.openEuler-24.03-LTS:
38.openEuler-24.03-LTS-Next:
39.openEuler-24.03-LTS-SP1:
40.openEuler-24.03-LTS-SP2:
41.master(6.12.33):
42.openEuler-20.03-LTS-SP4(4.19.90):
43.openEuler-22.03-LTS-SP3(5.10.0):
44.openEuler-22.03-LTS-SP4(5.10.0):
45.openEuler-24.03-LTS:
46.openEuler-24.03-LTS-Next:
47.openEuler-24.03-LTS-SP1:
48.openEuler-24.03-LTS-SP2:
49.master(6.12.33):
50.openEuler-20.03-LTS-SP4(4.19.90):
51.openEuler-22.03-LTS-SP3(5.10.0):
52.openEuler-22.03-LTS-SP4(5.10.0):
53.openEuler-24.03-LTS:
54.openEuler-24.03-LTS-Next:
55.openEuler-24.03-LTS-SP1:
56.openEuler-24.03-LTS-SP2:
57.master(6.12.33):
58.openEuler-20.03-LTS-SP4(4.19.90):
59.openEuler-22.03-LTS-SP3(5.10.0):
60.openEuler-22.03-LTS-SP4(5.10.0):
61.openEuler-24.03-LTS:
62.openEuler-24.03-LTS-Next:
63.openEuler-24.03-LTS-SP1:
64.openEuler-24.03-LTS-SP2:
65.master(6.12.33):
66.openEuler-20.03-LTS-SP4(4.19.90):
67.openEuler-22.03-LTS-SP3(5.10.0):
68.openEuler-22.03-LTS-SP4(5.10.0):
69.openEuler-24.03-LTS:
70.openEuler-24.03-LTS-Next:
71.openEuler-24.03-LTS-SP1:
72.openEuler-24.03-LTS-SP2:
73.master(6.12.33):
74.openEuler-20.03-LTS-SP4(4.19.90):
75.openEuler-22.03-LTS-SP3(5.10.0):
76.openEuler-22.03-LTS-SP4(5.10.0):
77.openEuler-24.03-LTS:
78.openEuler-24.03-LTS-Next:
79.openEuler-24.03-LTS-SP1:
80.openEuler-24.03-LTS-SP2:
81.master(6.12.33):
82.openEuler-20.03-LTS-SP4(4.19.90):
83.openEuler-22.03-LTS-SP3(5.10.0):
84.openEuler-22.03-LTS-SP4(5.10.0):
85.openEuler-24.03-LTS:
86.openEuler-24.03-LTS-Next:
87.openEuler-24.03-LTS-SP1:
88.openEuler-24.03-LTS-SP2:
89.master(6.12.33):
90.openEuler-20.03-LTS-SP4(4.19.90):
91.openEuler-22.03-LTS-SP3(5.10.0):
92.mas

原因说明：
  1.master(6.12.33):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP3(5.10.0):
4.openEuler-22.03-LTS-SP4(5.10.0):
5.openEuler-24.03-LTS:
6.openEuler-24.03-LTS-Next:
7.openEuler-24.03-LTS-SP1:
8.openEuler-24.03-LTS-SP2:

src-openEuler/kernel
关闭

内容风险标识

评论 (21)

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

内容风险标识

CVE-2021-47230

评论 (21)

搜索帮助

src-openEuler/kernel
关闭