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

  - 已解決 Linux 核心中的下列弱點：rcutorture: Fix ksoftirqd boosting timing and iteration The RCU priority boosting can fail in two situations: 1) If (nr_cpus= > maxcpus=), which means if the total number of CPUs is higher than those brought online at boot, then torture_onoff() may later bring up CPUs that weren't online on boot. Now since rcutorture initialization only boosts the ksoftirqds of the CPUs that have been set online on boot, the CPUs later set online by torture_onoff won't benefit from the boost, making RCU priority boosting fail. 2) The ksoftirqd kthreads are boosted after the creation of rcu_torture_boost() kthreads, which opens a window large enough for these rcu_torture_boost() kthreads to wait (despite running at FIFO priority) for ksoftirqds that are still running at SCHED_NORMAL priority. The issues can trigger for example with: ./kvm.sh --configs TREE01 --kconfig CONFIG_RCU_BOOST=y [ 34.968561] rcu-torture: !!! [ 34.968627] ------------[ cut here ]------------ [35.014054] WARNING: CPU: 4 PID: 114 at kernel/rcu/rcutorture.c:1979 rcu_torture_stats_print+0x5ad/0x610 [35.052043] Modules linked in: [ 35.069138] CPU: 4 PID: 114 Comm: rcu_torture_sta Not tainted 5.18.0-rc1 #1 [ 35.096424] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014 [ 35.154570] RIP:
    0010:rcu_torture_stats_print+0x5ad/0x610 [ 35.198527] Code: 63 1b 02 00 74 02 0f 0b 48 83 3d 35 63 1b 02 00 74 02 0f 0b 48 83 3d 21 63 1b 02 00 74 02 0f 0b 48 83 3d 0d 63 1b 02 00 74 02 <0f> 0b 83 eb 01 0f 8e ba fc ff ff 0f 0b e9 b3 fc ff f82 [ 37.251049] RSP: 0000:ffffa92a0050bdf8 EFLAGS: 00010202 [ 37.277320] rcu:
    De-offloading 8 [ 37.290367] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000001 [37.290387] RDX: 0000000000000000 RSI: 00000000ffffbfff RDI: 00000000ffffffff [ 37.290398] RBP:
    000000000000007b R08: 0000000000000000 R09: c0000000ffffbfff [ 37.290407] R10: 000000000000002a R11:
    ffffa92a0050bc18 R12: ffffa92a0050be20 [ 37.290417] R13: ffffa92a0050be78 R14: 0000000000000000 R15:
    000000000001bea0 [ 37.290427] FS: 0000000000000000(0000) GS:ffff96045eb00000(0000) knlGS:0000000000000000 [ 37.290448] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 37.290460] CR2: 0000000000000000 CR3:
    000000001dc0c000 CR4: 00000000000006e0 [ 37.290470] Call Trace: [ 37.295049] <TASK> [ 37.295065] ? preempt_count_add+0x63/0x90 [ 37.295095] ? _raw_spin_lock_irqsave+0x12/0x40 [ 37.295125] ? rcu_torture_stats_print+0x610/0x610 [ 37.295143] rcu_torture_stats+0x29/0x70 [ 37.295160] kthread+0xe3/0x110 [ 37.295176] ? kthread_complete_and_exit+0x20/0x20 [ 37.295193] ret_from_fork+0x22/0x30 [ 37.295218] </TASK> Fix this with boosting the ksoftirqds kthreads from the boosting hotplug callback itself and before the boosting kthreads are created. (CVE-2022-50177)

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

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

  - 已修复 Linux 内核中的下列漏洞：rcutorture: Fix ksoftirqd boosting timing and iteration The RCU priority boosting can fail in two situations: 1) If (nr_cpus= > maxcpus=), which means if the total number of CPUs is higher than those brought online at boot, then torture_onoff() may later bring up CPUs that weren't online on boot. Now since rcutorture initialization only boosts the ksoftirqds of the CPUs that have been set online on boot, the CPUs later set online by torture_onoff won't benefit from the boost, making RCU priority boosting fail. 2) The ksoftirqd kthreads are boosted after the creation of rcu_torture_boost() kthreads, which opens a window large enough for these rcu_torture_boost() kthreads to wait (despite running at FIFO priority) for ksoftirqds that are still running at SCHED_NORMAL priority. The issues can trigger for example with: ./kvm.sh --configs TREE01 --kconfig CONFIG_RCU_BOOST=y [ 34.968561] rcu-torture: !!! [ 34.968627] ------------[ cut here ]------------ [35.014054] WARNING: CPU: 4 PID: 114 at kernel/rcu/rcutorture.c:1979 rcu_torture_stats_print+0x5ad/0x610 [35.052043] Modules linked in: [ 35.069138] CPU: 4 PID: 114 Comm: rcu_torture_sta Not tainted 5.18.0-rc1 #1 [ 35.096424] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014 [ 35.154570] RIP:
    0010:rcu_torture_stats_print+0x5ad/0x610 [ 35.198527] Code: 63 1b 02 00 74 02 0f 0b 48 83 3d 35 63 1b 02 00 74 02 0f 0b 48 83 3d 21 63 1b 02 00 74 02 0f 0b 48 83 3d 0d 63 1b 02 00 74 02 <0f> 0b 83 eb 01 0f 8e ba fc ff ff 0f 0b e9 b3 fc ff f82 [ 37.251049] RSP: 0000:ffffa92a0050bdf8 EFLAGS: 00010202 [ 37.277320] rcu:
    De-offloading 8 [ 37.290367] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000001 [37.290387] RDX: 0000000000000000 RSI: 00000000ffffbfff RDI: 00000000ffffffff [ 37.290398] RBP:
    000000000000007b R08: 0000000000000000 R09: c0000000ffffbfff [ 37.290407] R10: 000000000000002a R11:
    ffffa92a0050bc18 R12: ffffa92a0050be20 [ 37.290417] R13: ffffa92a0050be78 R14: 0000000000000000 R15:
    000000000001bea0 [ 37.290427] FS: 0000000000000000(0000) GS:ffff96045eb00000(0000) knlGS:0000000000000000 [ 37.290448] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 37.290460] CR2: 0000000000000000 CR3:
    000000001dc0c000 CR4: 00000000000006e0 [ 37.290470] Call Trace: [ 37.295049] <TASK> [ 37.295065] ? preempt_count_add+0x63/0x90 [ 37.295095] ? _raw_spin_lock_irqsave+0x12/0x40 [ 37.295125] ? rcu_torture_stats_print+0x610/0x610 [ 37.295143] rcu_torture_stats+0x29/0x70 [ 37.295160] kthread+0xe3/0x110 [ 37.295176] ? kthread_complete_and_exit+0x20/0x20 [ 37.295193] ret_from_fork+0x22/0x30 [ 37.295218] </TASK> Fix this with boosting the ksoftirqds kthreads from the boosting hotplug callback itself and before the boosting kthreads are created. (CVE-2022-50177)

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

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

  - 核心：路徑外攻擊者可能會插入資料或終止受害者的 TCP 工作階段 (CVE-2020-36516)

  - 核心：當 vc_cons[i].d 已經是 NULL 時，VT_RESIZEX ioctl 中的爭用條件可導致 NULL 指標解除參照 (CVE-2020-36558)

  - 核心：drivers/media/v4l2-core/v4l2-ioctl.c 中 video_usercopy 函式的大型引數可觸發記憶體洩漏弱點 (CVE-2021-30002)

  - 核心：sco_sock_sendmsg() 函式中的釋放後使用弱點 (CVE-2021-3640)

  - 核心：smb2_ioctl_query_info 的 NULL 指標解除參照弱點 (CVE-2022-0168)

  - 核心：回寫期間，udf_expand_file_adinicbdue() 中發生 NULL 指標解除參照 (CVE-2022-0617)

  - 核心：DMA_FROM_DEVICE 的 swiotlb 資訊洩漏弱點 (CVE-2022-0854)

  - 核心：nft_do_chain 中堆疊上未初始化的暫存器可造成 UM 核心指標洩漏 (CVE-2022-1016)

  - 核心：snd_pcm_hw_free 中的爭用條件可導致釋放後使用 (CVE-2022-1048)

  - 核心：net/sched/cls_api.c 的 tc_new_tfilter() 中的釋放後使用弱點 (CVE-2022-1055)

  - 核心：KVM：cmpxchg_gpte 可寫入使用者空間區域之外的 pfns (

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

  - 内核：路径外攻击者可能会注入数据或终止受害者的 TCP 会话 (CVE-2020-36516)

  - 内核：当 vc_cons[i].d 已经为空时，VT_RESIZEX ioctl 中存在争用条件，从而导致空指针取消引用 (CVE-2020-36558)

  - 内核：drivers/media/v4l2-core/v4l2-ioctl.c 中的 video_usercopy 函数中存在大型参数的内存泄漏 (CVE-2021-30002)

  - 内核：函数 sco_sock_sendmsg() 中存在释放后使用漏洞 (CVE-2021-3640)

  - 内核：smb2_ioctl_query_info 空指针取消引用 (CVE-2022-0168)

  - 内核：回写期间，udf_expand_file_adinicbdue() 中发生空指针取消引用 (CVE-2022-0617)

  - 内核：DMA_FROM_DEVICE 的 swiotlb 信息泄漏 (CVE-2022-0854)

  - 内核：nft_do_chain 中堆栈上未初始化的寄存器可导致内核指针泄漏到 UM (CVE-2022-1016)

  - 内核：snd_pcm_hw_free 中的争用条件导致释放后使用 (CVE-2022-1048)

  - 内核：net/sched/cls_api.c 的 tc_new_tfilter() 中的释放后使用漏洞 (CVE-2022-1055)

  - 内核：KVM：cmpxchg_gpte 可在用户空间区域之外写入 pfns (CVE-2022-1158)

  - 内核：当挂载和操作已损坏的映像时，ext4 中存在释放后使用和内存错误 (CVE-2022-1184)

  - 内核：x86_emulate_insn 中的空指针取消引用可能导致 DoS (CVE-2022-1852)

  - 内核：net/packet：packet_recvmsg() 中存在 slab-of-bounds 访问 (CVE-2022-20368)

  - 内核：nft_set_desc_concat_parse() 中存在缓冲区溢出漏洞 (CVE-2022-2078)

  - 内核：可以使用调试程序将零写入所选位置 (CVE-2022-21499)

  - hw：cpu：arm64: Spectre-BHB (CVE-2022-23960)

  - 内核：nfs_atomic_open() 返回未初始化的数据，而不是 ENOTDIR (CVE-2022-24448)

  - 内核：nf_tables 潜在的跨表释放后使用可能导致本地特权提升 (CVE-2022-2586)

  - hw：cpu：- Intel：Return Stack Buffer 屏障后预测 (CVE-2022-26373)

  - 内核：openvswitch: 整数下溢导致 reserve_sfa_size() 中的越界写入 (CVE-2022-2639)

  - 内核：drivers/hid/hid-elo.c 中存在内存泄漏 (CVE-2022-27950)

  - 内核：drivers/net/can/usb/ems_usb.c 中的 ems_usb_start_xmit 中存在双重释放漏洞。(CVE-2022-28390)

  - 内核：SUNRPC 子系统中存在释放后使用 (CVE-2022-28893)

  - 内核：psi 触发器在轮询期间遭到破坏时存在释放后使用漏洞 (CVE-2022-2938)

  - 内核：由于未正确更新 net/sched/cls_u32.c 中的引用计数而导致释放后使用 (CVE-2022-29581)

  - 内核：net/netfilter/nfnetlink_queue.c 中的 nfqnl_mangle 中存在 DoS (CVE-2022-36946)

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

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

  - kernel: パス外の攻撃者が、データを注入したり、被害者の TCP セッションを終了したりする可能性があります (CVE-2020-36516)

  - kernel: vc_cons[i].d がすでに NULL の場合に VT_RESIZEX ioctl で競合状態が発生し、NULL ポインターデリファレンスが引き起こされます (CVE-2020-36558)

  - kernel: drivers/media/v4l2-core/v4l2-ioctl.c の video_usercopy 関数の大きな引数によるメモリリーク (CVE-2021-30002)

  - kernel: 関数 sco_sock_sendmsg() でのメモリ解放後使用 (Use After Free) の脆弱性 (CVE-2021-3640)

  - kernel: smb2_ioctl_query_info NULLポインターデリファレンス (CVE-2022-0168)

  - kernel: ライトバック中の udf_expand_file_adinicbdue() における NULL ポインターデリファレンス (CVE-2022-0617)

  - kernel: DMA_FROM_DEVICE による swiotlb 情報漏洩 (CVE-2022-0854)

  - kernel: nft_do_chain のスタックの初期化されていないレジスタにより、カーネルポインターが UM に漏洩する可能性があります (CVE-2022-1016)

  - kernel: snd_pcm_hw_free の競合状態によりメモリ解放後使用 (Use After Free) が発生 (CVE-2022-1048)

  - kernel: net/sched/cls_api.c の tc_new_tfilter() のメモリ解放後使用 (Use-After-Free) (CVE-2022-1055)

  - kernel: KVM: cmpxchg_gpte は、ユーザー空間領域外の pfns に書き込むことができます (CVE-2022-1158)

  - kernel: 破損したイメージをマウントおよび操作する際の ext4 のメモリ解放後使用 (Use After Free) およびメモリエラー (CVE-2022-1184)

  - kernel: x86_emulate_insn の NULL ポインターデリファレンスにより、DoS が発生する可能性があります (CVE-2022-1852)

  - kernel: net/packet：packet_recvmsg() の slab-out-of-bounds アクセス (CVE-2022-20368)

  - kernel: nft_set_desc_concat_parse() のバッファオーバーフロー (CVE-2022-2078)

  - kernel: 選択した場所にゼロを書き込むためにデバッガーを使用することが可能 (CVE-2022-21499)

  - hw：cpu：arm64: Spectre-BHB (CVE-2022-23960)

  - kernel: nfs_atomic_open() は、ENOTDIR の代わりに初期化されていないデータを返します (CVE-2022-24448)

  - kernel: nf_tables クロステーブルの潜在的なメモリ解放後使用 (Use After Free) により、ローカルの権限昇格が引き起こされる可能性があります (CVE-2022-2586)

  - hw：cpu: Intel: ポストバリアリターンスタックバッファ予測 (CVE-2022-26373)

  - kernel: openvswitch: 整数アンダーフローにより、reserve_sfa_size() で領域外書き込みが発生します (CVE-2022-2639)

  - kernel: drivers/hid/hid-elo.c のメモリリーク (CVE-2022-27950)

  - kernel: drivers/net/can/usb/ems_usb.c の ems_usb_start_xmit にある二重解放 (CVE-2022-28390)

  - kernel: SUNRPC サブシステムでのメモリ解放後使用 (Use After Free) (CVE-2022-28893)

  - kernel: ポーリング中にpsiトリガーが破壊されたときのuse-after-free (CVE-2022-2938)

  - kernel: net/sched/cls_u32.c の参照カウントの不適切な更新によるメモリ解放後使用 (Use After Free) (CVE-2022-29581)

  - kernel: net/netfilter/nfnetlink_queue.c の nfqnl_mangle の DoS (CVE-2022-36946)

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

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

  - Linux カーネルでは、以下の脆弱性が解決されています: rcutorture: Fix ksoftirqd boosting timing and iteration The RCU priority boosting can fail in two situations: 1) If (nr_cpus= > maxcpus=), which means if the total number of CPUs is higher than those brought online at boot, then torture_onoff() may later bring up CPUs that weren't online on boot. Now since rcutorture initialization only boosts the ksoftirqds of the CPUs that have been set online on boot, the CPUs later set online by torture_onoff won't benefit from the boost, making RCU priority boosting fail. 2) The ksoftirqd kthreads are boosted after the creation of rcu_torture_boost() kthreads, which opens a window large enough for these rcu_torture_boost() kthreads to wait (despite running at FIFO priority) for ksoftirqds that are still running at SCHED_NORMAL priority. The issues can trigger for example with: ./kvm.sh --configs TREE01 --kconfig CONFIG_RCU_BOOST=y [ 34.968561] rcu-torture: !!! [ 34.968627] ------------[ cut here ]------------ [35.014054] WARNING: CPU: 4 PID: 114 at kernel/rcu/rcutorture.c:1979 rcu_torture_stats_print+0x5ad/0x610 [35.052043] Modules linked in: [ 35.069138] CPU: 4 PID: 114 Comm: rcu_torture_sta Not tainted 5.18.0-rc1 #1 [ 35.096424] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014 [ 35.154570] RIP:
    0010:rcu_torture_stats_print+0x5ad/0x610 [ 35.198527] Code: 63 1b 02 00 74 02 0f 0b 48 83 3d 35 63 1b 02 00 74 02 0f 0b 48 83 3d 21 63 1b 02 00 74 02 0f 0b 48 83 3d 0d 63 1b 02 00 74 02 <0f> 0b 83 eb 01 0f 8e ba fc ff ff 0f 0b e9 b3 fc ff f82 [ 37.251049] RSP: 0000:ffffa92a0050bdf8 EFLAGS: 00010202 [ 37.277320] rcu:
    De-offloading 8 [ 37.290367] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000001 [37.290387] RDX: 0000000000000000 RSI: 00000000ffffbfff RDI: 00000000ffffffff [ 37.290398] RBP:
    000000000000007b R08: 0000000000000000 R09: c0000000ffffbfff [ 37.290407] R10: 000000000000002a R11:
    ffffa92a0050bc18 R12: ffffa92a0050be20 [ 37.290417] R13: ffffa92a0050be78 R14: 0000000000000000 R15:
    000000000001bea0 [ 37.290427] FS: 0000000000000000(0000) GS:ffff96045eb00000(0000) knlGS:0000000000000000 [ 37.290448] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 37.290460] CR2: 0000000000000000 CR3:
    000000001dc0c000 CR4: 00000000000006e0 [ 37.290470] Call Trace: [ 37.295049] <TASK> [ 37.295065] ? preempt_count_add+0x63/0x90 [ 37.295095] ? _raw_spin_lock_irqsave+0x12/0x40 [ 37.295125] ? rcu_torture_stats_print+0x610/0x610 [ 37.295143] rcu_torture_stats+0x29/0x70 [ 37.295160] kthread+0xe3/0x110 [ 37.295176] ? kthread_complete_and_exit+0x20/0x20 [ 37.295193] ret_from_fork+0x22/0x30 [ 37.295218] </TASK> Fix this with boosting the ksoftirqds kthreads from the boosting hotplug callback itself and before the boosting kthreads are created. (CVE-2022-50177)

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

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

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

    Security Fix(es):

    * off-path attacker may inject data or terminate victim's TCP session (CVE-2020-36516)

    * race condition in VT_RESIZEX ioctl when vc_cons[i].d is already NULL leading to NULL pointer dereference     (CVE-2020-36558)

    * use-after-free vulnerability in function sco_sock_sendmsg() (CVE-2021-3640)

    * memory leak for large arguments in video_usercopy function in drivers/media/v4l2-core/v4l2-ioctl.c     (CVE-2021-30002)

    * smb2_ioctl_query_info NULL Pointer Dereference (CVE-2022-0168)

    * NULL pointer dereference in udf_expand_file_adinicbdue() during writeback (CVE-2022-0617)

    * swiotlb information leak with DMA_FROM_DEVICE (CVE-2022-0854)

    * uninitialized registers on stack in nft_do_chain can cause kernel pointer leakage to UM (CVE-2022-1016)

    * race condition in snd_pcm_hw_free leading to use-after-free (CVE-2022-1048)

    * use-after-free in tc_new_tfilter() in net/sched/cls_api.c (CVE-2022-1055)

    * use-after-free and memory errors in ext4 when mounting and operating on a corrupted image     (CVE-2022-1184)

    * NULL pointer dereference in x86_emulate_insn may lead to DoS (CVE-2022-1852)

    * buffer overflow in nft_set_desc_concat_parse() (CVE-2022-2078)

    * nf_tables cross-table potential use-after-free may lead to local privilege escalation (CVE-2022-2586)

    * openvswitch: integer underflow leads to out-of-bounds write in reserve_sfa_size() (CVE-2022-2639)

    * use-after-free when psi trigger is destroyed while being polled (CVE-2022-2938)

    * net/packet: slab-out-of-bounds access in packet_recvmsg() (CVE-2022-20368)

    * possible to use the debugger to write zero into a location of choice (CVE-2022-21499)

    * Spectre-BHB (CVE-2022-23960)

    * Post-barrier Return Stack Buffer Predictions (CVE-2022-26373)

    * memory leak in drivers/hid/hid-elo.c (CVE-2022-27950)

    * double free in ems_usb_start_xmit in drivers/net/can/usb/ems_usb.c (CVE-2022-28390)

    * use after free in SUNRPC subsystem (CVE-2022-28893)

    * use-after-free due to improper update of reference count in net/sched/cls_u32.c (CVE-2022-29581)

    * DoS in nfqnl_mangle in net/netfilter/nfnetlink_queue.c (CVE-2022-36946)

    * nfs_atomic_open() returns uninitialized data instead of ENOTDIR (CVE-2022-24448)

    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.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 8.7 Release Notes     linked from the References section.

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: rcutorture: Fix ksoftirqd boosting     timing and iteration The RCU priority boosting can fail in two situations: 1) If (nr_cpus= > maxcpus=),     which means if the total number of CPUs is higher than those brought online at boot, then torture_onoff()     may later bring up CPUs that weren't online on boot. Now since rcutorture initialization only boosts the     ksoftirqds of the CPUs that have been set online on boot, the CPUs later set online by torture_onoff won't     benefit from the boost, making RCU priority boosting fail. 2) The ksoftirqd kthreads are boosted after the     creation of rcu_torture_boost() kthreads, which opens a window large enough for these rcu_torture_boost()     kthreads to wait (despite running at FIFO priority) for ksoftirqds that are still running at SCHED_NORMAL     priority. The issues can trigger for example with: ./kvm.sh --configs TREE01 --kconfig     CONFIG_RCU_BOOST=y [ 34.968561] rcu-torture: !!! [ 34.968627] ------------[ cut here ]------------ [     35.014054] WARNING: CPU: 4 PID: 114 at kernel/rcu/rcutorture.c:1979 rcu_torture_stats_print+0x5ad/0x610 [     35.052043] Modules linked in: [ 35.069138] CPU: 4 PID: 114 Comm: rcu_torture_sta Not tainted 5.18.0-rc1 #1     [ 35.096424] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS     rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014 [ 35.154570] RIP:
    0010:rcu_torture_stats_print+0x5ad/0x610 [ 35.198527] Code: 63 1b 02 00 74 02 0f 0b 48 83 3d 35 63 1b 02     00 74 02 0f 0b 48 83 3d 21 63 1b 02 00 74 02 0f 0b 48 83 3d 0d 63 1b 02 00 74 02 <0f> 0b 83 eb 01 0f 8e ba     fc ff ff 0f 0b e9 b3 fc ff f82 [ 37.251049] RSP: 0000:ffffa92a0050bdf8 EFLAGS: 00010202 [ 37.277320] rcu:
    De-offloading 8 [ 37.290367] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000001 [     37.290387] RDX: 0000000000000000 RSI: 00000000ffffbfff RDI: 00000000ffffffff [ 37.290398] RBP:
    000000000000007b R08: 0000000000000000 R09: c0000000ffffbfff [ 37.290407] R10: 000000000000002a R11:
    ffffa92a0050bc18 R12: ffffa92a0050be20 [ 37.290417] R13: ffffa92a0050be78 R14: 0000000000000000 R15:
    000000000001bea0 [ 37.290427] FS: 0000000000000000(0000) GS:ffff96045eb00000(0000) knlGS:0000000000000000     [ 37.290448] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 37.290460] CR2: 0000000000000000 CR3:
    000000001dc0c000 CR4: 00000000000006e0 [ 37.290470] Call Trace: [ 37.295049] <TASK> [ 37.295065] ?     preempt_count_add+0x63/0x90 [ 37.295095] ? _raw_spin_lock_irqsave+0x12/0x40 [ 37.295125] ?     rcu_torture_stats_print+0x610/0x610 [ 37.295143] rcu_torture_stats+0x29/0x70 [ 37.295160]     kthread+0xe3/0x110 [ 37.295176] ? kthread_complete_and_exit+0x20/0x20 [ 37.295193] ret_from_fork+0x22/0x30     [ 37.295218] </TASK> Fix this with boosting the ksoftirqds kthreads from the boosting hotplug callback     itself and before the boosting kthreads are created. (CVE-2022-50177)

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

ID	Name	Product	Family	Published	Updated	Severity
245781	Linux Distros 未修補的弱點：CVE-2022-50177	Nessus	Misc.	8/8/2025	7/17/2026	medium
210815	RHEL 9：核心 (RHSA-2024:9315)	Nessus	Red Hat Local Security Checks	11/12/2024	3/24/2026	high
245781	Linux Distros 未修补的漏洞：CVE-2022-50177	Nessus	Misc.	8/8/2025	7/17/2026	medium
210815	RHEL 9：内核 (RHSA-2024:9315)	Nessus	Red Hat Local Security Checks	11/12/2024	3/24/2026	high
167155	RHEL 8：核心 (RHSA-2022: 7683)	Nessus	Red Hat Local Security Checks	11/9/2022	11/20/2025	high
167155	RHEL 8：内核 (RHSA-2022: 7683)	Nessus	Red Hat Local Security Checks	11/9/2022	11/20/2025	high
167155	RHEL 8: カーネル (RHSA-2022: 7683)	Nessus	Red Hat Local Security Checks	11/9/2022	11/20/2025	high
245781	Linux Distros のパッチ未適用の脆弱性: CVE-2022-50177	Nessus	Misc.	8/8/2025	7/17/2026	medium
210815	RHEL 9 : kernel (RHSA-2024:9315)	Nessus	Red Hat Local Security Checks	11/12/2024	3/24/2026	high
167155	RHEL 8 : kernel (RHSA-2022:7683)	Nessus	Red Hat Local Security Checks	11/9/2022	11/20/2025	high
245781	Linux Distros Unpatched Vulnerability : CVE-2022-50177	Nessus	Misc.	8/8/2025	7/17/2026	medium
210815	RHEL 9 : kernel (RHSA-2024:9315)	Nessus	Red Hat Local Security Checks	11/12/2024	3/24/2026	high

Detections

Analytics

Plugins Search

medium

high

medium

high

high

high

high

medium

high

high

medium

high