リモート Redhat Enterprise Linux 8 ホストにインストールされているパッケージは、RHSA-2022: 6460 のアドバイザリに記載されている複数の脆弱性の影響を受けます。

  - hw:  cpu: マルチコア共有バッファ (別名 SBDR) の不完全なクリーンアップ (CVE-2022-21123)

  - hw:  cpu: マイクロアーキテクチャのフィルバッファ (別名 SBDS) の不完全なクリーンアップ (CVE-2022-21125)

  - hw:  cpu: 特定の特殊レジスター書き込み操作 (別名 DRPW) の不完全なクリーンアップ (CVE-2022-21166)

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションの自己報告されたバージョン番号にのみ依存しています。

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2022:6460 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * Incomplete cleanup of multi-core shared buffers (aka SBDR) (CVE-2022-21123)

    * Incomplete cleanup of microarchitectural fill buffers (aka SBDS) (CVE-2022-21125)

    * Incomplete cleanup in specific special register write operations (aka DRPW) (CVE-2022-21166)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Bug Fix(es):

    * Bad page state in process qemu-kvm  pfn:68a74600 (BZ#2081013)

    * slub corruption during  LPM of hnv interface (BZ#2081250)

    * Affinity broken due to vector space exhaustion (BZ#2084646)

    * 'rmmod pmt_telemetry' panics on ADL-P IOTG (BZ#2091079)

    * Unable to boot RHEL-8.6 on Brazos max. config (Install is success) (BZ#2092241)

    * kernel crash after reboot of T14/G2 AMD laptop (mt7921e module) (BZ#2095654)

    * mt7921: free resources on pci_probe error path (BZ#2101684)

    * NLM should be more defensive if underlying FS changes fl_owner (BZ#2102099)

    * RHEL8/async-pf Guest call trace when reboot after postcopy migration with high stress workload     (BZ#2105340)

    * execve exit tracepoint not called (BZ#2106662)

    * QProcess dead lock on kernel-4.18.0-358 (BZ#2107643)

    * KVM fix guest FPU uABI size to kvm_xsave (BZ#2107652)

    * KVM selftests fail to compile (BZ#2107655)

    * Some monitor have no display with AMD W6400 when boot into OS. (BZ#2109826)

    * Percpu counter usage is gradually getting increasing during podman container recreation. (BZ#2110039)

    * multipath failed to recover after EEH hit on flavafish adapter on     Denali(qla2xxx/flavafish/RHEL8.6/Denali) (BZ#2110768)

    * soft lockups under heavy I/O load to ahci connected SSDs (BZ#2110772)

    * trouble re-assigning MACs to VFs, ice stricter than other drivers (BZ#2111936)

    * Intel MPI 2019.0 - mpirun stuck on latest kernel (BZ#2112030)

    * Multicast packets are not received by all VFs on the same port even though they have the same VLAN     (BZ#2117026)

    * Hyper-V 2019 Dynamic Memory Problem hv_balloon (BZ#2117050)

    * kernel BUG at kernel/sched/deadline.c:1561! (BZ#2117410)

    * ALSA (sound) driver - update Intel SOF kcontrol code (BZ#2117732)

    * bridge over bond over ice ports has no connection (BZ#2118580)

    * Fix max VLANs available for VF (BZ#2118581)

    * offline selftest failed (BZ#2118582)

    * INTEL NVMUpdate utility ver 3.20 is failing to update firmware on E810-XXVDA4T (WPC) (BZ#2118583)

    * VM configured with failover interface will coredump after been migrating from source host to target     host(only iavf driver) (BZ#2118705)

    * Fix max VLANs available for untrusted VF (BZ#2118707)

    * Softlockup on infinite loop in task_get_css() for a CSS_DYING cpuset (BZ#2120776)

    Enhancement(s):

    * KVM Sapphire Rapids (SPR) AMX Instructions (BZ#2088287)

    * KVM Sapphire Rapids (SPR) AMX Instructions part2 (BZ#2088288)

    * ice: Driver Update (BZ#2102359)

    * iavf: Driver Update (BZ#2102360)

    * iommu/vt-d: Make DMAR_UNITS_SUPPORTED a config setting (BZ#2112983)

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In the Linux kernel, the following vulnerability has been resolved: x86/fpu: KVM: Set the base guest FPU     uABI size to sizeof(struct kvm_xsave) Set the starting uABI size of KVM's guest FPU to 'struct kvm_xsave',     i.e. to KVM's historical uABI size. When saving FPU state for usersapce, KVM (well, now the FPU) sets the     FP+SSE bits in the XSAVE header even if the host doesn't support XSAVE. Setting the XSAVE header allows     the VM to be migrated to a host that does support XSAVE without the new host having to handle FPU state     that may or may not be compatible with XSAVE. Setting the uABI size to the host's default size results in     out-of-bounds writes (setting the FP+SSE bits) and data corruption (that is thankfully caught by KASAN)     when running on hosts without XSAVE, e.g. on Core2 CPUs. WARN if the default size is larger than KVM's     historical uABI size; all features that can push the FPU size beyond the historical size must be opt-in.
    ================================================================== BUG: KASAN: slab-out-of-bounds in     fpu_copy_uabi_to_guest_fpstate+0x86/0x130 Read of size 8 at addr ffff888011e33a00 by task qemu-build/681     CPU: 1 PID: 681 Comm: qemu-build Not tainted 5.18.0-rc5-KASAN-amd64 #1 Hardware name: /DG35EC, BIOS     ECG3510M.86A.0118.2010.0113.1426 01/13/2010 Call Trace: <TASK> dump_stack_lvl+0x34/0x45     print_report.cold+0x45/0x575 kasan_report+0x9b/0xd0 fpu_copy_uabi_to_guest_fpstate+0x86/0x130     kvm_arch_vcpu_ioctl+0x72a/0x1c50 [kvm] kvm_vcpu_ioctl+0x47f/0x7b0 [kvm] __x64_sys_ioctl+0x5de/0xc90     do_syscall_64+0x31/0x50 entry_SYSCALL_64_after_hwframe+0x44/0xae </TASK> Allocated by task 0: (stack is     not available) The buggy address belongs to the object at ffff888011e33800 which belongs to the cache     kmalloc-512 of size 512 The buggy address is located 0 bytes to the right of 512-byte region     [ffff888011e33800, ffff888011e33a00) The buggy address belongs to the physical page: page:0000000089cd4adb     refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x11e30 head:0000000089cd4adb order:2     compound_mapcount:0 compound_pincount:0 flags: 0x4000000000010200(slab|head|zone=1) raw: 4000000000010200     dead000000000100 dead000000000122 ffff888001041c80 raw: 0000000000000000 0000000080100010 00000001ffffffff     0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address:
    ffff888011e33900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888011e33980: 00 00 00 00 00 00 00     00 00 00 00 00 00 00 00 00 >ffff888011e33a00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ^     ffff888011e33a80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff888011e33b00: fc fc fc fc fc fc fc     fc fc fc fc fc fc fc fc fc ================================================================== Disabling     lock debugging due to kernel taint (CVE-2022-49557)

Note that Nessus relies on the presence of the package as reported by the vendor.

Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - 已修复 Linux 内核中的下列漏洞：x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave) Set the starting uABI size of KVM's guest FPU to 'struct kvm_xsave', i.e. to KVM's historical uABI size. When saving FPU state for usersapce, KVM (well, now the FPU) sets the FP+SSE bits in the XSAVE header even if the host doesn't support XSAVE. Setting the XSAVE header allows the VM to be migrated to a host that does support XSAVE without the new host having to handle FPU state that may or may not be compatible with XSAVE. Setting the uABI size to the host's default size results in out-of-bounds writes (setting the FP+SSE bits) and data corruption (that is thankfully caught by KASAN) when running on hosts without XSAVE, e.g. on Core2 CPUs. WARN if the default size is larger than KVM's historical uABI size; all features that can push the FPU size beyond the historical size must be opt-in.
    ================================================================== BUG: KASAN: slab-out-of-bounds in fpu_copy_uabi_to_guest_fpstate+0x86/0x130 Read of size 8 at addr ffff888011e33a00 by task qemu-build/681 CPU: 1 PID: 681 Comm: qemu-build Not tainted 5.18.0-rc5-KASAN-amd64 #1 Hardware name: /DG35EC, BIOS ECG3510M.86A.0118.2010.0113.1426 01/13/2010 Call Trace: <TASK> dump_stack_lvl+0x34/0x45 print_report.cold+0x45/0x575 kasan_report+0x9b/0xd0 fpu_copy_uabi_to_guest_fpstate+0x86/0x130 kvm_arch_vcpu_ioctl+0x72a/0x1c50 [kvm] kvm_vcpu_ioctl+0x47f/0x7b0 [kvm] __x64_sys_ioctl+0x5de/0xc90 do_syscall_64+0x31/0x50 entry_SYSCALL_64_after_hwframe+0x44/0xae </TASK> Allocated by task 0: (stack is not available) The buggy address belongs to the object at ffff888011e33800 which belongs to the cache kmalloc-512 of size 512 The buggy address is located 0 bytes to the right of 512-byte region [ffff888011e33800, ffff888011e33a00) The buggy address belongs to the physical page: page:0000000089cd4adb refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x11e30 head:0000000089cd4adb order:2 compound_mapcount:0 compound_pincount:0 flags: 0x4000000000010200(slab|head|zone=1) raw: 4000000000010200 dead000000000100 dead000000000122 ffff888001041c80 raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address:
    ffff888011e33900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888011e33980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff888011e33a00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ^ ffff888011e33a80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff888011e33b00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ================================================================== Disabling lock debugging due to kernel taint (CVE-2022-49557)

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

远程 Redhat Enterprise Linux 8 主机上安装的程序包受到 RHSA-2022: 6460 公告中提及的多个漏洞影响。

  - hw：cpu：多核共享缓冲区清理不完全（也称为 SBDR）(CVE-2022-21123)

  - hw：cpu：微架构填充缓冲区清理不完全（也称为 SBDS）(CVE-2022-21125)

  - hw：cpu：特定特殊寄存器写入操作清理不完全（也称为 DRPW）(CVE-2022-21166)

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

遠端 Redhat Enterprise Linux 8 主機上安裝的套件受到 RHSA-2022: 6460 公告中提及的多個弱點影響。

  - hw：cpu：未完全清理多核心共用緩衝區 (即 SBDR) (CVE-2022-21123)

  - hw：cpu：未完全清理微架構填充緩衝區 (即 SBDS) (CVE-2022-21125)

  - hw：cpu：特定的特殊暫存器寫入作業中存在不完全清理 (即 DRPW) (CVE-2022-21166)

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且供應商未提供可用的修補程式。

  - 已解決 Linux 核心中的下列弱點：x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave) Set the starting uABI size of KVM's guest FPU to 'struct kvm_xsave', i.e. to KVM's historical uABI size. When saving FPU state for usersapce, KVM (well, now the FPU) sets the FP+SSE bits in the XSAVE header even if the host doesn't support XSAVE. Setting the XSAVE header allows the VM to be migrated to a host that does support XSAVE without the new host having to handle FPU state that may or may not be compatible with XSAVE. Setting the uABI size to the host's default size results in out-of-bounds writes (setting the FP+SSE bits) and data corruption (that is thankfully caught by KASAN) when running on hosts without XSAVE, e.g. on Core2 CPUs. WARN if the default size is larger than KVM's historical uABI size; all features that can push the FPU size beyond the historical size must be opt-in.
    ================================================================== BUG: KASAN: slab-out-of-bounds in fpu_copy_uabi_to_guest_fpstate+0x86/0x130 Read of size 8 at addr ffff888011e33a00 by task qemu-build/681 CPU: 1 PID: 681 Comm: qemu-build Not tainted 5.18.0-rc5-KASAN-amd64 #1 Hardware name: /DG35EC, BIOS ECG3510M.86A.0118.2010.0113.1426 01/13/2010 Call Trace: <TASK> dump_stack_lvl+0x34/0x45 print_report.cold+0x45/0x575 kasan_report+0x9b/0xd0 fpu_copy_uabi_to_guest_fpstate+0x86/0x130 kvm_arch_vcpu_ioctl+0x72a/0x1c50 [kvm] kvm_vcpu_ioctl+0x47f/0x7b0 [kvm] __x64_sys_ioctl+0x5de/0xc90 do_syscall_64+0x31/0x50 entry_SYSCALL_64_after_hwframe+0x44/0xae </TASK> Allocated by task 0: (stack is not available) The buggy address belongs to the object at ffff888011e33800 which belongs to the cache kmalloc-512 of size 512 The buggy address is located 0 bytes to the right of 512-byte region [ffff888011e33800, ffff888011e33a00) The buggy address belongs to the physical page: page:0000000089cd4adb refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x11e30 head:0000000089cd4adb order:2 compound_mapcount:0 compound_pincount:0 flags: 0x4000000000010200(slab|head|zone=1) raw: 4000000000010200 dead000000000100 dead000000000122 ffff888001041c80 raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address:
    ffff888011e33900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888011e33980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff888011e33a00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ^ ffff888011e33a80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff888011e33b00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ================================================================== Disabling lock debugging due to kernel taint (CVE-2022-49557)

請注意，Nessus 依賴供應商報告的套件存在。

Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - Linux カーネルでは、以下の脆弱性が解決されています: x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave) Set the starting uABI size of KVM's guest FPU to 'struct kvm_xsave', i.e. to KVM's historical uABI size. When saving FPU state for usersapce, KVM (well, now the FPU) sets the FP+SSE bits in the XSAVE header even if the host doesn't support XSAVE. Setting the XSAVE header allows the VM to be migrated to a host that does support XSAVE without the new host having to handle FPU state that may or may not be compatible with XSAVE. Setting the uABI size to the host's default size results in out-of-bounds writes (setting the FP+SSE bits) and data corruption (that is thankfully caught by KASAN) when running on hosts without XSAVE, e.g. on Core2 CPUs. WARN if the default size is larger than KVM's historical uABI size; all features that can push the FPU size beyond the historical size must be opt-in.
    ================================================================== BUG: KASAN: slab-out-of-bounds in fpu_copy_uabi_to_guest_fpstate+0x86/0x130 Read of size 8 at addr ffff888011e33a00 by task qemu-build/681 CPU: 1 PID: 681 Comm: qemu-build Not tainted 5.18.0-rc5-KASAN-amd64 #1 Hardware name: /DG35EC, BIOS ECG3510M.86A.0118.2010.0113.1426 01/13/2010 Call Trace: <TASK> dump_stack_lvl+0x34/0x45 print_report.cold+0x45/0x575 kasan_report+0x9b/0xd0 fpu_copy_uabi_to_guest_fpstate+0x86/0x130 kvm_arch_vcpu_ioctl+0x72a/0x1c50 [kvm] kvm_vcpu_ioctl+0x47f/0x7b0 [kvm] __x64_sys_ioctl+0x5de/0xc90 do_syscall_64+0x31/0x50 entry_SYSCALL_64_after_hwframe+0x44/0xae </TASK> Allocated by task 0: (stack is not available) The buggy address belongs to the object at ffff888011e33800 which belongs to the cache kmalloc-512 of size 512 The buggy address is located 0 bytes to the right of 512-byte region [ffff888011e33800, ffff888011e33a00) The buggy address belongs to the physical page: page:0000000089cd4adb refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x11e30 head:0000000089cd4adb order:2 compound_mapcount:0 compound_pincount:0 flags: 0x4000000000010200(slab|head|zone=1) raw: 4000000000010200 dead000000000100 dead000000000122 ffff888001041c80 raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address:
    ffff888011e33900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888011e33980: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff888011e33a00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ^ ffff888011e33a80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff888011e33b00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ================================================================== Disabling lock debugging due to kernel taint (CVE-2022-49557)

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

ID	名稱	產品	系列	已發布	已更新	嚴重性
164964	RHEL 8: カーネル (RHSA-2022: 6460)	Nessus	Red Hat Local Security Checks	2022/9/13	2025/8/15	high
164964	RHEL 8 : kernel (RHSA-2022:6460)	Nessus	Red Hat Local Security Checks	2022/9/13	2025/8/15	high
249482	Linux Distros Unpatched Vulnerability : CVE-2022-49557	Nessus	Misc.	2025/8/15	2025/8/15	high
249482	Linux Distros 未修补的漏洞：CVE-2022-49557	Nessus	Misc.	2025/8/15	2025/8/15	high
164964	RHEL 8：内核 (RHSA-2022: 6460)	Nessus	Red Hat Local Security Checks	2022/9/13	2025/8/15	high
164964	RHEL 8：核心 (RHSA-2022: 6460)	Nessus	Red Hat Local Security Checks	2022/9/13	2025/8/15	high
249482	Linux Distros 未修補的弱點：CVE-2022-49557	Nessus	Misc.	2025/8/15	2025/8/15	high
249482	Linux Distros のパッチ未適用の脆弱性: CVE-2022-49557	Nessus	Misc.	2025/8/15	2025/8/15	high

偵測

搜尋 Plugin

high

high

high

high

high

high

high

high