Sign in
Sign up
Explore
Enterprise
Education
Search
Help
Terms of use
About Us
Explore
Enterprise
Education
Gitee Premium
Gitee AI
AI teammates
Sign in
Sign up
Fetch the repository succeeded.
description of repo status
Open Source
>
Other
>
Operation System
&&
Watch
Unwatch
Watching
Releases Only
Ignoring
128
Star
73
Fork
331
src-openEuler
/
kernel
Closed
Code
Issues
1197
Pull Requests
35
Wiki
Insights
Pipelines
Service
JavaDoc
PHPDoc
Quality Analysis
Jenkins for Gitee
Tencent CloudBase
Tencent Cloud Serverless
悬镜安全
Aliyun SAE
Codeblitz
SBOM
DevLens
Don’t show this again
Update failed. Please try again later!
Remove this flag
Content Risk Flag
This task is identified by
as the content contains sensitive information such as code security bugs, privacy leaks, etc., so it is only accessible to contributors of this repository.
CVE-2022-48916
Done
#IALPU1
CVE和安全问题
openeuler-ci-bot
owner
Opened this issue
2024-08-22 12:19
一、漏洞信息 漏洞编号:[CVE-2022-48916](https://nvd.nist.gov/vuln/detail/CVE-2022-48916) 漏洞归属组件:[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:iommu/vt-d: Fix double list_add when enabling VMD in scalable modeWhen enabling VMD and IOMMU scalable mode, the following kernel paniccall trace/kernel log is shown in Eagle Stream platform (Sapphire RapidsCPU) during booting:pci 0000:59:00.5: Adding to iommu group 42...vmd 0000:59:00.5: PCI host bridge to bus 10000:80pci 10000:80:01.0: [8086:352a] type 01 class 0x060400pci 10000:80:01.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]pci 10000:80:01.0: enabling Extended Tagspci 10000:80:01.0: PME# supported from D0 D3hot D3coldpci 10000:80:01.0: DMAR: Setup RID2PASID failedpci 10000:80:01.0: Failed to add to iommu group 42: -16pci 10000:80:03.0: [8086:352b] type 01 class 0x060400pci 10000:80:03.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]pci 10000:80:03.0: enabling Extended Tagspci 10000:80:03.0: PME# supported from D0 D3hot D3cold------------[ cut here ]------------kernel BUG at lib/list_debug.c:29!invalid opcode: 0000 [#1] PREEMPT SMP NOPTICPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.17.0-rc3+ #7Hardware name: Lenovo ThinkSystem SR650V3/SB27A86647, BIOS ESE101Y-1.00 01/13/2022Workqueue: events work_for_cpu_fnRIP: 0010:__list_add_valid.cold+0x26/0x3fCode: 9a 4a ab ff 4c 89 c1 48 c7 c7 40 0c d9 9e e8 b9 b1 fe ff 0f 0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 f0 0c d9 9e e8 a2 b1 fe ff <0f> 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 98 0c d9 9e e8 8b b1 feRSP: 0000:ff5ad434865b3a40 EFLAGS: 00010246RAX: 0000000000000058 RBX: ff4d61160b74b880 RCX: ff4d61255e1fffa8RDX: 0000000000000000 RSI: 00000000fffeffff RDI: ffffffff9fd34f20RBP: ff4d611d8e245c00 R08: 0000000000000000 R09: ff5ad434865b3888R10: ff5ad434865b3880 R11: ff4d61257fdc6fe8 R12: ff4d61160b74b8a0R13: ff4d61160b74b8a0 R14: ff4d611d8e245c10 R15: ff4d611d8001ba70FS: 0000000000000000(0000) GS:ff4d611d5ea00000(0000) knlGS:0000000000000000CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: ff4d611fa1401000 CR3: 0000000aa0210001 CR4: 0000000000771ef0DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400PKRU: 55555554Call Trace: <TASK> intel_pasid_alloc_table+0x9c/0x1d0 dmar_insert_one_dev_info+0x423/0x540 ? device_to_iommu+0x12d/0x2f0 intel_iommu_attach_device+0x116/0x290 __iommu_attach_device+0x1a/0x90 iommu_group_add_device+0x190/0x2c0 __iommu_probe_device+0x13e/0x250 iommu_probe_device+0x24/0x150 iommu_bus_notifier+0x69/0x90 blocking_notifier_call_chain+0x5a/0x80 device_add+0x3db/0x7b0 ? arch_memremap_can_ram_remap+0x19/0x50 ? memremap+0x75/0x140 pci_device_add+0x193/0x1d0 pci_scan_single_device+0xb9/0xf0 pci_scan_slot+0x4c/0x110 pci_scan_child_bus_extend+0x3a/0x290 vmd_enable_domain.constprop.0+0x63e/0x820 vmd_probe+0x163/0x190 local_pci_probe+0x42/0x80 work_for_cpu_fn+0x13/0x20 process_one_work+0x1e2/0x3b0 worker_thread+0x1c4/0x3a0 ? rescuer_thread+0x370/0x370 kthread+0xc7/0xf0 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30 </TASK>Modules linked in:---[ end trace 0000000000000000 ]---...Kernel panic - not syncing: Fatal exceptionKernel Offset: 0x1ca00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)---[ end Kernel panic - not syncing: Fatal exception ]---The following lspci output shows devices 10000:80:* are subdevices ofthe VMD device 0000:59:00.5: $ lspci ... 0000:59:00.5 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller (rev 20) ... 10000:80:01.0 PCI bridge: Intel Corporation Device 352a (rev 03) 10000:80:03.0 PCI bridge: Intel Corporation Device 352b (rev 03) 10000:80:05.0 PCI bridge: Intel Corporation Device 352c (rev 03) 10000:80:07.0 PCI bridge: Intel Corporation Device 352d (rev 03) 10000:81:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller] 10000:82:00---truncated--- 漏洞公开时间:2024-08-22 10:15:05 漏洞创建时间:2024-08-22 12:19:27 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2022-48916 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2aaa085bd012a83be7104356301828585a2253ed | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/b00833768e170a31af09268f7ab96aecfcca9623 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/d5ad4214d9c6c6e465c192789020a091282dfee7 | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48916 | https://bugzilla.suse.com/show_bug.cgi?id=1229638 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2022-48916 | https://bugzilla.suse.com/show_bug.cgi?id=1229638 | | suse_bugzilla | https://git.kernel.org/stable/c/2aaa085bd012a83be7104356301828585a2253ed | https://bugzilla.suse.com/show_bug.cgi?id=1229638 | | suse_bugzilla | https://git.kernel.org/stable/c/b00833768e170a31af09268f7ab96aecfcca9623 | https://bugzilla.suse.com/show_bug.cgi?id=1229638 | | suse_bugzilla | https://git.kernel.org/stable/c/d5ad4214d9c6c6e465c192789020a091282dfee7 | https://bugzilla.suse.com/show_bug.cgi?id=1229638 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2022/CVE-2022-48916.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1229638 | | ubuntu | https://www.cve.org/CVERecord?id=CVE-2022-48916 | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://git.kernel.org/linus/b00833768e170a31af09268f7ab96aecfcca9623 (5.17-rc7) | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://git.kernel.org/stable/c/2aaa085bd012a83be7104356301828585a2253ed | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://git.kernel.org/stable/c/d5ad4214d9c6c6e465c192789020a091282dfee7 | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://git.kernel.org/stable/c/b00833768e170a31af09268f7ab96aecfcca9623 | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2022-48916 | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://launchpad.net/bugs/cve/CVE-2022-48916 | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://security-tracker.debian.org/tracker/CVE-2022-48916 | https://ubuntu.com/security/CVE-2022-48916 | | amazon_linux_explore | https://access.redhat.com/security/cve/CVE-2022-48916 | https://explore.alas.aws.amazon.com/CVE-2022-48916.html | | amazon_linux_explore | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48916 | https://explore.alas.aws.amazon.com/CVE-2022-48916.html | </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/2aaa085bd012a83be7104356301828585a2253ed | | nvd | | | | https://git.kernel.org/stable/c/b00833768e170a31af09268f7ab96aecfcca9623 | | nvd | | | | https://git.kernel.org/stable/c/d5ad4214d9c6c6e465c192789020a091282dfee7 | | nvd | | linux | | https://git.kernel.org/linus/b00833768e170a31af09268f7ab96aecfcca9623 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:iommu/vt-d: Fix double list_add when enabling VMD in scalable modeWhen enabling VMD and IOMMU scalable mode, the following kernel paniccall trace/kernel log is shown in Eagle Stream platform (Sapphire RapidsCPU) during booting:pci 0000:59:00.5: Adding to iommu group 42...vmd 0000:59:00.5: PCI host bridge to bus 10000:80pci 10000:80:01.0: [8086:352a] type 01 class 0x060400pci 10000:80:01.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]pci 10000:80:01.0: enabling Extended Tagspci 10000:80:01.0: PME# supported from D0 D3hot D3coldpci 10000:80:01.0: DMAR: Setup RID2PASID failedpci 10000:80:01.0: Failed to add to iommu group 42: -16pci 10000:80:03.0: [8086:352b] type 01 class 0x060400pci 10000:80:03.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]pci 10000:80:03.0: enabling Extended Tagspci 10000:80:03.0: PME# supported from D0 D3hot D3cold------------[ cut here ]------------kernel BUG at lib/list_debug.c:29!invalid opcode: 0000 [#1] PREEMPT SMP NOPTICPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.17.0-rc3+ #7Hardware name: Lenovo ThinkSystem SR650V3/SB27A86647, BIOS ESE101Y-1.00 01/13/2022Workqueue: events work_for_cpu_fnRIP: 0010:__list_add_valid.cold+0x26/0x3fCode: 9a 4a ab ff 4c 89 c1 48 c7 c7 40 0c d9 9e e8 b9 b1 fe ff 0f 0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 f0 0c d9 9e e8 a2 b1 fe ff <0f> 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 98 0c d9 9e e8 8b b1 feRSP: 0000:ff5ad434865b3a40 EFLAGS: 00010246RAX: 0000000000000058 RBX: ff4d61160b74b880 RCX: ff4d61255e1fffa8RDX: 0000000000000000 RSI: 00000000fffeffff RDI: ffffffff9fd34f20RBP: ff4d611d8e245c00 R08: 0000000000000000 R09: ff5ad434865b3888R10: ff5ad434865b3880 R11: ff4d61257fdc6fe8 R12: ff4d61160b74b8a0R13: ff4d61160b74b8a0 R14: ff4d611d8e245c10 R15: ff4d611d8001ba70FS: 0000000000000000(0000) GS:ff4d611d5ea00000(0000) knlGS:0000000000000000CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: ff4d611fa1401000 CR3: 0000000aa0210001 CR4: 0000000000771ef0DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400PKRU: 55555554Call Trace: <TASK> intel_pasid_alloc_table+0x9c/0x1d0 dmar_insert_one_dev_info+0x423/0x540 ? device_to_iommu+0x12d/0x2f0 intel_iommu_attach_device+0x116/0x290 __iommu_attach_device+0x1a/0x90 iommu_group_add_device+0x190/0x2c0 __iommu_probe_device+0x13e/0x250 iommu_probe_device+0x24/0x150 iommu_bus_notifier+0x69/0x90 blocking_notifier_call_chain+0x5a/0x80 device_add+0x3db/0x7b0 ? arch_memremap_can_ram_remap+0x19/0x50 ? memremap+0x75/0x140 pci_device_add+0x193/0x1d0 pci_scan_single_device+0xb9/0xf0 pci_scan_slot+0x4c/0x110 pci_scan_child_bus_extend+0x3a/0x290 vmd_enable_domain.constprop.0+0x63e/0x820 vmd_probe+0x163/0x190 local_pci_probe+0x42/0x80 work_for_cpu_fn+0x13/0x20 process_one_work+0x1e2/0x3b0 worker_thread+0x1c4/0x3a0 ? rescuer_thread+0x370/0x370 kthread+0xc7/0xf0 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30 </TASK>Modules linked in:---[ end trace 0000000000000000 ]---...Kernel panic - not syncing: Fatal exceptionKernel Offset: 0x1ca00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)---[ end Kernel panic - not syncing: Fatal exception ]---The following lspci output shows devices 10000:80:* are subdevices ofthe VMD device 0000:59:00.5: $ lspci ... 0000:59:00.5 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller (rev 20) ... 10000:80:01.0 PCI bridge: Intel Corporation Device 352a (rev 03) 10000:80:03.0 PCI bridge: Intel Corporation Device 352b (rev 03) 10000:80:05.0 PCI bridge: Intel Corporation Device 352c (rev 03) 10000:80:07.0 PCI bridge: Intel Corporation Device 352d (rev 03) 10000:81:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller] 10000:82:00---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-22.03-LTS-SP1(5.10.0):受影响 2.openEuler-22.03-LTS-SP3(5.10.0):受影响 3.openEuler-22.03-LTS-SP4(5.10.0):受影响 4.openEuler-20.03-LTS-SP4(4.19.90):不受影响 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
一、漏洞信息 漏洞编号:[CVE-2022-48916](https://nvd.nist.gov/vuln/detail/CVE-2022-48916) 漏洞归属组件:[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:iommu/vt-d: Fix double list_add when enabling VMD in scalable modeWhen enabling VMD and IOMMU scalable mode, the following kernel paniccall trace/kernel log is shown in Eagle Stream platform (Sapphire RapidsCPU) during booting:pci 0000:59:00.5: Adding to iommu group 42...vmd 0000:59:00.5: PCI host bridge to bus 10000:80pci 10000:80:01.0: [8086:352a] type 01 class 0x060400pci 10000:80:01.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]pci 10000:80:01.0: enabling Extended Tagspci 10000:80:01.0: PME# supported from D0 D3hot D3coldpci 10000:80:01.0: DMAR: Setup RID2PASID failedpci 10000:80:01.0: Failed to add to iommu group 42: -16pci 10000:80:03.0: [8086:352b] type 01 class 0x060400pci 10000:80:03.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]pci 10000:80:03.0: enabling Extended Tagspci 10000:80:03.0: PME# supported from D0 D3hot D3cold------------[ cut here ]------------kernel BUG at lib/list_debug.c:29!invalid opcode: 0000 [#1] PREEMPT SMP NOPTICPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.17.0-rc3+ #7Hardware name: Lenovo ThinkSystem SR650V3/SB27A86647, BIOS ESE101Y-1.00 01/13/2022Workqueue: events work_for_cpu_fnRIP: 0010:__list_add_valid.cold+0x26/0x3fCode: 9a 4a ab ff 4c 89 c1 48 c7 c7 40 0c d9 9e e8 b9 b1 fe ff 0f 0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 f0 0c d9 9e e8 a2 b1 fe ff <0f> 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 98 0c d9 9e e8 8b b1 feRSP: 0000:ff5ad434865b3a40 EFLAGS: 00010246RAX: 0000000000000058 RBX: ff4d61160b74b880 RCX: ff4d61255e1fffa8RDX: 0000000000000000 RSI: 00000000fffeffff RDI: ffffffff9fd34f20RBP: ff4d611d8e245c00 R08: 0000000000000000 R09: ff5ad434865b3888R10: ff5ad434865b3880 R11: ff4d61257fdc6fe8 R12: ff4d61160b74b8a0R13: ff4d61160b74b8a0 R14: ff4d611d8e245c10 R15: ff4d611d8001ba70FS: 0000000000000000(0000) GS:ff4d611d5ea00000(0000) knlGS:0000000000000000CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: ff4d611fa1401000 CR3: 0000000aa0210001 CR4: 0000000000771ef0DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400PKRU: 55555554Call Trace: <TASK> intel_pasid_alloc_table+0x9c/0x1d0 dmar_insert_one_dev_info+0x423/0x540 ? device_to_iommu+0x12d/0x2f0 intel_iommu_attach_device+0x116/0x290 __iommu_attach_device+0x1a/0x90 iommu_group_add_device+0x190/0x2c0 __iommu_probe_device+0x13e/0x250 iommu_probe_device+0x24/0x150 iommu_bus_notifier+0x69/0x90 blocking_notifier_call_chain+0x5a/0x80 device_add+0x3db/0x7b0 ? arch_memremap_can_ram_remap+0x19/0x50 ? memremap+0x75/0x140 pci_device_add+0x193/0x1d0 pci_scan_single_device+0xb9/0xf0 pci_scan_slot+0x4c/0x110 pci_scan_child_bus_extend+0x3a/0x290 vmd_enable_domain.constprop.0+0x63e/0x820 vmd_probe+0x163/0x190 local_pci_probe+0x42/0x80 work_for_cpu_fn+0x13/0x20 process_one_work+0x1e2/0x3b0 worker_thread+0x1c4/0x3a0 ? rescuer_thread+0x370/0x370 kthread+0xc7/0xf0 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30 </TASK>Modules linked in:---[ end trace 0000000000000000 ]---...Kernel panic - not syncing: Fatal exceptionKernel Offset: 0x1ca00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)---[ end Kernel panic - not syncing: Fatal exception ]---The following lspci output shows devices 10000:80:* are subdevices ofthe VMD device 0000:59:00.5: $ lspci ... 0000:59:00.5 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller (rev 20) ... 10000:80:01.0 PCI bridge: Intel Corporation Device 352a (rev 03) 10000:80:03.0 PCI bridge: Intel Corporation Device 352b (rev 03) 10000:80:05.0 PCI bridge: Intel Corporation Device 352c (rev 03) 10000:80:07.0 PCI bridge: Intel Corporation Device 352d (rev 03) 10000:81:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller] 10000:82:00---truncated--- 漏洞公开时间:2024-08-22 10:15:05 漏洞创建时间:2024-08-22 12:19:27 漏洞详情参考链接: https://nvd.nist.gov/vuln/detail/CVE-2022-48916 <details> <summary>更多参考(点击展开)</summary> | 参考来源 | 参考链接 | 来源链接 | | ------- | -------- | -------- | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2aaa085bd012a83be7104356301828585a2253ed | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/b00833768e170a31af09268f7ab96aecfcca9623 | | | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/d5ad4214d9c6c6e465c192789020a091282dfee7 | | | suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48916 | https://bugzilla.suse.com/show_bug.cgi?id=1229638 | | suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2022-48916 | https://bugzilla.suse.com/show_bug.cgi?id=1229638 | | suse_bugzilla | https://git.kernel.org/stable/c/2aaa085bd012a83be7104356301828585a2253ed | https://bugzilla.suse.com/show_bug.cgi?id=1229638 | | suse_bugzilla | https://git.kernel.org/stable/c/b00833768e170a31af09268f7ab96aecfcca9623 | https://bugzilla.suse.com/show_bug.cgi?id=1229638 | | suse_bugzilla | https://git.kernel.org/stable/c/d5ad4214d9c6c6e465c192789020a091282dfee7 | https://bugzilla.suse.com/show_bug.cgi?id=1229638 | | suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2022/CVE-2022-48916.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1229638 | | ubuntu | https://www.cve.org/CVERecord?id=CVE-2022-48916 | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://git.kernel.org/linus/b00833768e170a31af09268f7ab96aecfcca9623 (5.17-rc7) | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://git.kernel.org/stable/c/2aaa085bd012a83be7104356301828585a2253ed | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://git.kernel.org/stable/c/d5ad4214d9c6c6e465c192789020a091282dfee7 | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://git.kernel.org/stable/c/b00833768e170a31af09268f7ab96aecfcca9623 | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2022-48916 | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://launchpad.net/bugs/cve/CVE-2022-48916 | https://ubuntu.com/security/CVE-2022-48916 | | ubuntu | https://security-tracker.debian.org/tracker/CVE-2022-48916 | https://ubuntu.com/security/CVE-2022-48916 | | amazon_linux_explore | https://access.redhat.com/security/cve/CVE-2022-48916 | https://explore.alas.aws.amazon.com/CVE-2022-48916.html | | amazon_linux_explore | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48916 | https://explore.alas.aws.amazon.com/CVE-2022-48916.html | </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/2aaa085bd012a83be7104356301828585a2253ed | | nvd | | | | https://git.kernel.org/stable/c/b00833768e170a31af09268f7ab96aecfcca9623 | | nvd | | | | https://git.kernel.org/stable/c/d5ad4214d9c6c6e465c192789020a091282dfee7 | | nvd | | linux | | https://git.kernel.org/linus/b00833768e170a31af09268f7ab96aecfcca9623 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu | </details> 二、漏洞分析结构反馈 影响性分析说明: In the Linux kernel, the following vulnerability has been resolved:iommu/vt-d: Fix double list_add when enabling VMD in scalable modeWhen enabling VMD and IOMMU scalable mode, the following kernel paniccall trace/kernel log is shown in Eagle Stream platform (Sapphire RapidsCPU) during booting:pci 0000:59:00.5: Adding to iommu group 42...vmd 0000:59:00.5: PCI host bridge to bus 10000:80pci 10000:80:01.0: [8086:352a] type 01 class 0x060400pci 10000:80:01.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]pci 10000:80:01.0: enabling Extended Tagspci 10000:80:01.0: PME# supported from D0 D3hot D3coldpci 10000:80:01.0: DMAR: Setup RID2PASID failedpci 10000:80:01.0: Failed to add to iommu group 42: -16pci 10000:80:03.0: [8086:352b] type 01 class 0x060400pci 10000:80:03.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]pci 10000:80:03.0: enabling Extended Tagspci 10000:80:03.0: PME# supported from D0 D3hot D3cold------------[ cut here ]------------kernel BUG at lib/list_debug.c:29!invalid opcode: 0000 [#1] PREEMPT SMP NOPTICPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.17.0-rc3+ #7Hardware name: Lenovo ThinkSystem SR650V3/SB27A86647, BIOS ESE101Y-1.00 01/13/2022Workqueue: events work_for_cpu_fnRIP: 0010:__list_add_valid.cold+0x26/0x3fCode: 9a 4a ab ff 4c 89 c1 48 c7 c7 40 0c d9 9e e8 b9 b1 fe ff 0f 0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 f0 0c d9 9e e8 a2 b1 fe ff <0f> 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 98 0c d9 9e e8 8b b1 feRSP: 0000:ff5ad434865b3a40 EFLAGS: 00010246RAX: 0000000000000058 RBX: ff4d61160b74b880 RCX: ff4d61255e1fffa8RDX: 0000000000000000 RSI: 00000000fffeffff RDI: ffffffff9fd34f20RBP: ff4d611d8e245c00 R08: 0000000000000000 R09: ff5ad434865b3888R10: ff5ad434865b3880 R11: ff4d61257fdc6fe8 R12: ff4d61160b74b8a0R13: ff4d61160b74b8a0 R14: ff4d611d8e245c10 R15: ff4d611d8001ba70FS: 0000000000000000(0000) GS:ff4d611d5ea00000(0000) knlGS:0000000000000000CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: ff4d611fa1401000 CR3: 0000000aa0210001 CR4: 0000000000771ef0DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400PKRU: 55555554Call Trace: <TASK> intel_pasid_alloc_table+0x9c/0x1d0 dmar_insert_one_dev_info+0x423/0x540 ? device_to_iommu+0x12d/0x2f0 intel_iommu_attach_device+0x116/0x290 __iommu_attach_device+0x1a/0x90 iommu_group_add_device+0x190/0x2c0 __iommu_probe_device+0x13e/0x250 iommu_probe_device+0x24/0x150 iommu_bus_notifier+0x69/0x90 blocking_notifier_call_chain+0x5a/0x80 device_add+0x3db/0x7b0 ? arch_memremap_can_ram_remap+0x19/0x50 ? memremap+0x75/0x140 pci_device_add+0x193/0x1d0 pci_scan_single_device+0xb9/0xf0 pci_scan_slot+0x4c/0x110 pci_scan_child_bus_extend+0x3a/0x290 vmd_enable_domain.constprop.0+0x63e/0x820 vmd_probe+0x163/0x190 local_pci_probe+0x42/0x80 work_for_cpu_fn+0x13/0x20 process_one_work+0x1e2/0x3b0 worker_thread+0x1c4/0x3a0 ? rescuer_thread+0x370/0x370 kthread+0xc7/0xf0 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30 </TASK>Modules linked in:---[ end trace 0000000000000000 ]---...Kernel panic - not syncing: Fatal exceptionKernel Offset: 0x1ca00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)---[ end Kernel panic - not syncing: Fatal exception ]---The following lspci output shows devices 10000:80:* are subdevices ofthe VMD device 0000:59:00.5: $ lspci ... 0000:59:00.5 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller (rev 20) ... 10000:80:01.0 PCI bridge: Intel Corporation Device 352a (rev 03) 10000:80:03.0 PCI bridge: Intel Corporation Device 352b (rev 03) 10000:80:05.0 PCI bridge: Intel Corporation Device 352c (rev 03) 10000:80:07.0 PCI bridge: Intel Corporation Device 352d (rev 03) 10000:81:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller] 10000:82:00---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-22.03-LTS-SP1(5.10.0):受影响 2.openEuler-22.03-LTS-SP3(5.10.0):受影响 3.openEuler-22.03-LTS-SP4(5.10.0):受影响 4.openEuler-20.03-LTS-SP4(4.19.90):不受影响 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
Comments (
22
)
Sign in
to comment
Status
Done
Backlog
已挂起
Doing
Done
Declined
Assignees
Not set
sanglipeng
sanglipeng
Assignee
Collaborator
+Assign
+Mention
Labels
CVE/FIXED
sig/Kernel
Not set
Projects
Unprojected
Unprojected
Pull Requests
None yet
None yet
Successfully merging a pull request will close this issue.
Branches
No related branch
Branches (
-
)
Tags (
-
)
Planed to start   -   Planed to end
-
Top level
Not Top
Top Level: High
Top Level: Medium
Top Level: Low
Priority
Not specified
Serious
Main
Secondary
Unimportant
Duration
(hours)
参与者(3)
1
https://gitee.com/src-openeuler/kernel.git
git@gitee.com:src-openeuler/kernel.git
src-openeuler
kernel
kernel
Going to Help Center
Search
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大,如何减小?
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release(发行版)
将 PHP 项目自动发布到 packagist.org
Comment
Repository Report
Back to the top
Login prompt
This operation requires login to the code cloud account. Please log in before operating.
Go to login
No account. Register