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

  - 已解決 Linux 核心中的下列弱點：bus: mhi: host: Range check CHDBOFF and ERDBOFF If the value read from the CHDBOFF and ERDBOFF registers is outside the range of the MHI register space then an invalid address might be computed which later causes a kernel panic. Range check the read value to prevent a crash due to bad data from the device. (CVE-2023-53598)

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

AlmaLinux 9.2 主機已安裝的套件會受到 TuxCare ALMALINUX9.2：CLSA-2026：1781347338 公告中提及的多個弱點影響。

  - 已解決 Linux 核心中的下列弱點：net: mdio: unexport __init-annotated mdio_bus_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the only in-tree call-site, drivers/net/phy/phy_device.c is never compiled as modular. (CONFIG_PHYLIB is boolean) (CVE-2022-49350)

  - 已解決 Linux 核心中的下列弱點：selinux: fix memleak in security_read_state_kernel() In this function, it directly returns the result of __security_read_policy without freeing the allocated memory in *data, cause memory leak issue, so free the memory if
    __security_read_policy failed. [PM: subject line tweak] (CVE-2022-50201)

  - 已解決 Linux 核心中的下列弱點：usb: typec: tcpci: fix of node refcount leak in tcpci_register_port() I got the following report while doing device(mt6370-tcpc) load test with CONFIG_OF_UNITTEST and CONFIG_OF_DYNAMIC enabled: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /i2c/pmic@34/tcpc/connector The 'fwnode' set in tcpci_parse_config() which is called in tcpci_register_port(), its node refcount is increased in device_get_named_child_node(). It needs be put while exiting, so call fwnode_handle_put() in the error path of tcpci_register_port() and in tcpci_unregister_port() to avoid leak. (CVE-2022-50246)

  - 已解決 Linux 核心中的下列弱點：drivers: serial: jsm: fix some leaks in probe This error path needs to unwind instead of just returning directly. (CVE-2022-50312)

  - 已解決 Linux 核心中的下列弱點：thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash When CPU 0 is offline and intel_powerclamp is used to inject idle, it generates kernel BUG: BUG: using smp_processor_id() in preemptible [00000000] code:
    bash/15687 caller is debug_smp_processor_id+0x17/0x20 CPU: 4 PID: 15687 Comm: bash Not tainted 5.19.0-rc7+ #57 Call Trace: <TASK> dump_stack_lvl+0x49/0x63 dump_stack+0x10/0x16 check_preemption_disabled+0xdd/0xe0 debug_smp_processor_id+0x17/0x20 powerclamp_set_cur_state+0x7f/0xf9 [intel_powerclamp] ... ... Here CPU 0 is the control CPU by default and changed to the current CPU, if CPU 0 offlined. This check has to be performed under cpus_read_lock(), hence the above warning. Use get_cpu() instead of smp_processor_id() to avoid this BUG. [ rjw: Subject edits ] (CVE-2022-50494)

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

AlmaLinux 9.2 主机上存在安装的程序包，该程序包受到 TuxCare ALMALINUX9.2：CLSA-2026：U 1781347338公告中提及的多个漏洞的影响。

  - 已修复 Linux 内核中的下列漏洞：net: mdio: unexport __init-annotated mdio_bus_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the only in-tree call-site, drivers/net/phy/phy_device.c is never compiled as modular. (CONFIG_PHYLIB is boolean) (CVE-2022-49350)

  - 已修复 Linux 内核中的下列漏洞：selinux: fix memleak in security_read_state_kernel() In this function, it directly returns the result of __security_read_policy without freeing the allocated memory in *data, cause memory leak issue, so free the memory if
    __security_read_policy failed. [PM: subject line tweak] (CVE-2022-50201)

  - 已修复 Linux 内核中的下列漏洞：usb: typec: tcpci: fix of node refcount leak in tcpci_register_port() I got the following report while doing device(mt6370-tcpc) load test with CONFIG_OF_UNITTEST and CONFIG_OF_DYNAMIC enabled: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /i2c/pmic@34/tcpc/connector The 'fwnode' set in tcpci_parse_config() which is called in tcpci_register_port(), its node refcount is increased in device_get_named_child_node(). It needs be put while exiting, so call fwnode_handle_put() in the error path of tcpci_register_port() and in tcpci_unregister_port() to avoid leak. (CVE-2022-50246)

  - 已修复 Linux 内核中的下列漏洞：drivers: serial: jsm: fix some leaks in probe This error path needs to unwind instead of just returning directly. (CVE-2022-50312)

  - 已修复 Linux 内核中的下列漏洞：thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash When CPU 0 is offline and intel_powerclamp is used to inject idle, it generates kernel BUG: BUG: using smp_processor_id() in preemptible [00000000] code:
    bash/15687 caller is debug_smp_processor_id+0x17/0x20 CPU: 4 PID: 15687 Comm: bash Not tainted 5.19.0-rc7+ #57 Call Trace: <TASK> dump_stack_lvl+0x49/0x63 dump_stack+0x10/0x16 check_preemption_disabled+0xdd/0xe0 debug_smp_processor_id+0x17/0x20 powerclamp_set_cur_state+0x7f/0xf9 [intel_powerclamp] ... ... Here CPU 0 is the control CPU by default and changed to the current CPU, if CPU 0 offlined. This check has to be performed under cpus_read_lock(), hence the above warning. Use get_cpu() instead of smp_processor_id() to avoid this BUG. [ rjw: Subject edits ] (CVE-2022-50494)

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

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

  - 已修复 Linux 内核中的下列漏洞：bus: mhi: host: Range check CHDBOFF and ERDBOFF If the value read from the CHDBOFF and ERDBOFF registers is outside the range of the MHI register space then an invalid address might be computed which later causes a kernel panic. Range check the read value to prevent a crash due to bad data from the device. (CVE-2023-53598)

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

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

  - Linux カーネルでは、以下の脆弱性が解決されています: bus: mhi: host: Range check CHDBOFF and ERDBOFF If the value read from the CHDBOFF and ERDBOFF registers is outside the range of the MHI register space then an invalid address might be computed which later causes a kernel panic. Range check the read value to prevent a crash due to bad data from the device. (CVE-2023-53598)

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

AlmaLinux 9.2 ホストには、TuxCare ALMALINUX9.2:CLSA-2026:1781347338アドバイザリに記載されている複数の脆弱性の影響を受けるパッケージがインストールされています。

  - Linux カーネルでは、以下の脆弱性が解決されています: net: mdio: unexport __init-annotated mdio_bus_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the only in-tree call-site, drivers/net/phy/phy_device.c is never compiled as modular. (CONFIG_PHYLIB is boolean) (CVE-2022-49350)

  - Linux カーネルでは、以下の脆弱性が解決されています: selinux: fix memleak in security_read_state_kernel() In this function, it directly returns the result of __security_read_policy without freeing the allocated memory in *data, cause memory leak issue, so free the memory if
    __security_read_policy failed. [PM: subject line tweak] (CVE-2022-50201)

  - Linux カーネルでは、以下の脆弱性が解決されています: usb: typec: tcpci: fix of node refcount leak in tcpci_register_port() I got the following report while doing device(mt6370-tcpc) load test with CONFIG_OF_UNITTEST and CONFIG_OF_DYNAMIC enabled: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /i2c/pmic@34/tcpc/connector The 'fwnode' set in tcpci_parse_config() which is called in tcpci_register_port(), its node refcount is increased in device_get_named_child_node(). It needs be put while exiting, so call fwnode_handle_put() in the error path of tcpci_register_port() and in tcpci_unregister_port() to avoid leak. (CVE-2022-50246)

  - Linux カーネルでは、以下の脆弱性が解決されています: drivers: serial: jsm: fix some leaks in probe This error path needs to unwind instead of just returning directly. (CVE-2022-50312)

  - Linux カーネルでは、以下の脆弱性が解決されています: thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash When CPU 0 is offline and intel_powerclamp is used to inject idle, it generates kernel BUG: BUG: using smp_processor_id() in preemptible [00000000] code:
    bash/15687 caller is debug_smp_processor_id+0x17/0x20 CPU: 4 PID: 15687 Comm: bash Not tainted 5.19.0-rc7+ #57 Call Trace: <TASK> dump_stack_lvl+0x49/0x63 dump_stack+0x10/0x16 check_preemption_disabled+0xdd/0xe0 debug_smp_processor_id+0x17/0x20 powerclamp_set_cur_state+0x7f/0xf9 [intel_powerclamp] ... ... Here CPU 0 is the control CPU by default and changed to the current CPU, if CPU 0 offlined. This check has to be performed under cpus_read_lock(), hence the above warning. Use get_cpu() instead of smp_processor_id() to avoid this BUG. [ rjw: Subject edits ] (CVE-2022-50494)

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

リモートの SUSE Linux SLES15 / SLES_SAP15 ホストには、SUSE-SU-2025:4320-1 のアドバイザリに記載された複数の脆弱性の影響を受けるパッケージがインストールされています。

    SUSE Linux Enterprise 15 SP5 のカーネルが更新され、いくつかの問題が修正されました。

    以下のセキュリティ問題が修正されました。

    - CVE-2022-50327:ACPI:プロセッサー:アイドル:acpi_fetch_acpi_dev() 戻り値(bsc#1249859)をチェックします。
    - CVE-2022-50334:hugetlbfs:hugetlbfs_parse_param() の null-ptr-deref を修正します(bsc#1249857)。
    - CVE-2022-50490:bpf:エラーを htab_lock_bucket() からユーザー空間(bsc#1251164)に伝播します。
    - CVE-2022-50516:fs:dlm:sb_lvbptr の無効な逆参照を修正します(bsc#1251741)。
    - CVE-2023-53365:ip6mr:ip6mr_cache_report() のskb_under_panicを修正します(bsc#1249988)。
    - CVE-2023-53500:xfrm:decode_session6 の slab-use-after-free を修正します(bsc#1250816)。
    - CVE-2023-53559:ip_vti:decode_session6 で起こり得る slab-use-after-free を修正します(bsc#1251052)。
    - CVE-2023-53574:wifi:rtw88:アンロード時にタイマーを削除し、skb キューを解放します(bsc#1251222)。
    - CVE-2023-53619:netfilter:conntrack:use-after-free nf_ct_helper_hashを回避します(bsc#1251743)。
    - CVE-2023-53673:Bluetooth:hci_event:conn を削除する前に disconnect コールバックを呼び出します(bsc#1251763)。
    - CVE-2023-53705:ipv6:ipv6_find_tlv() での領域外アクセスを修正します(bsc#1252554)。
    - CVE-2025-37885:KVM:x86:*新しい*ルートがポスト可能でない場合、IRTE をホストコントロールにリセットします(bsc#1242960)。
    - CVE-2025-38084:hugetlb:VMA を分割する際に、一部の PMD を共有しません(bsc#1245498)。
    - CVE-2025-38085:mm/hugetlb:huge_pmd_unshare() と GUP-fast の競合を修正します(bsc#1245499)。
    - CVE-2025-38476:rpl:rpl_do_srh_inline() の use-after-free を修正します(bsc#1247317)。
    - CVE-2025-39742:RDMA:hfi1:find_hw_thread_mask() でのゼロ除算の可能性を修正します(bsc#1249479)。
    - CVE-2025-39797:xfrm:SPI 処理の重複(bsc#1249608)。
    - CVE-2025-39945:cnic:cnic_delete_task における use-after-free のバグを修正します(bsc#1251230)。
    - CVE-2025-39967:fbcon:fbcon_do_set_font における整数オーバーフローを修正します(bsc#1252033)。
    - CVE-2025-39968:i40e:VF フィルターの最大境界検査を追加します(bsc#1252047)。
    - CVE-2025-39973:i40e:ring_len param の検証を追加します(bsc#1252035)。
    - CVE-2025-39978:octeontx2-pf:otx2_tc_add_flow() の use-after-free の可能性を修正します(bsc#1252069)。
    - CVE-2025-39981:Bluetooth:MGMT:可能性のある UAF を修正します(bsc#1252060)。
    - CVE-2025-40018:ipvs:netns クリーンアップ中の登録解除ip_vs_ftp延期します(bsc#1252688)。
    - CVE-2025-40044:fs:udf:lengthAllocDescs 処理における OOB 読み取りを修正します(bsc#1252785)。

    セキュリティに関係しない以下の問題が修正されました。

    - NFS:サーバーの委任リストから取り消された委任を削除します(bsc#1246211)。
    - NFSv4:FREE_STATEID による委任のクリーンアップを許可します(bsc#1246211)。
    - fbcon:フォント割り当てでの OOB アクセスを修正します(bsc#1252033)
    - NFSv4 の kabi 修正:FREE_STATEID による委任のクリーンアップを許可(bsc#1246211)。
    - kernel-subpackage-spec:モジュールに二重署名しません(bsc#1251930)。
    - mm:共有メモリタイプで不要なページ障害が終了するのを回避します(bsc#1251823)。
    - net:hv_netvsc:チャネルを開く際のホストからの早期受信イベントの損失を修正します(bsc#1252265)。
    - net:mana:ジャンボフレームのページプールに切り替えます(bsc#1248754)。
    - net:mana:メモリ効率を改善するために、ページ全体ではなくページプールフラグメントを RX バッファに使用します(bsc#1248754)。
    - netfilter:nft_objref:objref および objrefmap 式を検証します(bsc#1250237)。
    - rpm/check-for-config-changes:CONFIG_SCHED_PROXY_EXECも無視します(bsc#1250946)

Tenable は、前述の記述ブロックを SUSE セキュリティアドバイザリから直接抽出しています。

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

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: bus: mhi: host: Range check CHDBOFF     and ERDBOFF If the value read from the CHDBOFF and ERDBOFF registers is outside the range of the MHI     register space then an invalid address might be computed which later causes a kernel panic. Range check     the read value to prevent a crash due to bad data from the device. (CVE-2023-53598)

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

An update of the linux package has been released.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:4320-1 advisory.

    The SUSE Linux Enterprise 15 SP5 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2022-50327: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value (bsc#1249859).
    - CVE-2022-50334: hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() (bsc#1249857).
    - CVE-2022-50490: bpf: Propagate error from htab_lock_bucket() to userspace (bsc#1251164).
    - CVE-2022-50516: fs: dlm: fix invalid derefence of sb_lvbptr (bsc#1251741).
    - CVE-2023-53365: ip6mr: Fix skb_under_panic in ip6mr_cache_report() (bsc#1249988).
    - CVE-2023-53500: xfrm: fix slab-use-after-free in decode_session6 (bsc#1250816).
    - CVE-2023-53559: ip_vti: fix potential slab-use-after-free in decode_session6 (bsc#1251052).
    - CVE-2023-53574: wifi: rtw88: delete timer and free skb queue when unloading (bsc#1251222).
    - CVE-2023-53619: netfilter: conntrack: Avoid nf_ct_helper_hash uses after free (bsc#1251743).
    - CVE-2023-53673: Bluetooth: hci_event: call disconnect callback before deleting conn (bsc#1251763).
    - CVE-2023-53705: ipv6: Fix out-of-bounds access in ipv6_find_tlv() (bsc#1252554).
    - CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).
    - CVE-2025-38084: hugetlb: unshare some PMDs when splitting VMAs (bsc#1245498).
    - CVE-2025-38085: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245499).
    - CVE-2025-38476: rpl: Fix use-after-free in rpl_do_srh_inline() (bsc#1247317).
    - CVE-2025-39742: RDMA: hfi1: fix possible divide-by-zero in find_hw_thread_mask() (bsc#1249479).
    - CVE-2025-39797: xfrm: Duplicate SPI Handling (bsc#1249608).
    - CVE-2025-39945: cnic: Fix use-after-free bugs in cnic_delete_task (bsc#1251230).
    - CVE-2025-39967: fbcon: fix integer overflow in fbcon_do_set_font (bsc#1252033).
    - CVE-2025-39968: i40e: add max boundary check for VF filters (bsc#1252047).
    - CVE-2025-39973: i40e: add validation for ring_len param (bsc#1252035).
    - CVE-2025-39978: octeontx2-pf: Fix potential use after free in otx2_tc_add_flow() (bsc#1252069).
    - CVE-2025-39981: Bluetooth: MGMT: Fix possible UAFs (bsc#1252060).
    - CVE-2025-40018: ipvs: Defer ip_vs_ftp unregister during netns cleanup (bsc#1252688).
    - CVE-2025-40044: fs: udf: fix OOB read in lengthAllocDescs handling (bsc#1252785).

    The following non security issues were fixed:

    - NFS: remove revoked delegation from server's delegation list (bsc#1246211).
    - NFSv4: Allow FREE_STATEID to clean up delegations (bsc#1246211).
    - fbcon: Fix OOB access in font allocation (bsc#1252033)
    - kabi fix for NFSv4: Allow FREE_STATEID to clean up delegations (bsc#1246211).
    - kernel-subpackage-spec: Do not doubly-sign modules (bsc#1251930).
    - mm: avoid unnecessary page fault retires on shared memory types (bsc#1251823).
    - net: hv_netvsc: fix loss of early receive events from host during channel open (bsc#1252265).
    - net: mana: Switch to page pool for jumbo frames (bsc#1248754).
    - net: mana: Use page pool fragments for RX buffers instead of full pages to improve memory efficiency     (bsc#1248754).
    - netfilter: nft_objref: validate objref and objrefmap expressions (bsc#1250237).
    - rpm/check-for-config-changes: ignore CONFIG_SCHED_PROXY_EXEC, too (bsc#1250946)

Tenable has extracted the preceding description block directly from the SUSE 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 AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1781347338 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: net: mdio: unexport __init-annotated     mdio_bus_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up     after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol     may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I     fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways     to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the only in-     tree call-site, drivers/net/phy/phy_device.c is never compiled as modular. (CONFIG_PHYLIB is boolean)     (CVE-2022-49350)

  - In the Linux kernel, the following vulnerability has been resolved: selinux: fix memleak in     security_read_state_kernel() In this function, it directly returns the result of __security_read_policy     without freeing the allocated memory in *data, cause memory leak issue, so free the memory if
    __security_read_policy failed. [PM: subject line tweak] (CVE-2022-50201)

  - In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpci: fix of node     refcount leak in tcpci_register_port() I got the following report while doing device(mt6370-tcpc) load     test with CONFIG_OF_UNITTEST and CONFIG_OF_DYNAMIC enabled: OF: ERROR: memory leak, expected refcount 1     instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node     /i2c/pmic@34/tcpc/connector The 'fwnode' set in tcpci_parse_config() which is called in     tcpci_register_port(), its node refcount is increased in device_get_named_child_node(). It needs be put     while exiting, so call fwnode_handle_put() in the error path of tcpci_register_port() and in     tcpci_unregister_port() to avoid leak. (CVE-2022-50246)

  - In the Linux kernel, the following vulnerability has been resolved: drivers: serial: jsm: fix some leaks     in probe This error path needs to unwind instead of just returning directly. (CVE-2022-50312)

  - In the Linux kernel, the following vulnerability has been resolved: thermal: intel_powerclamp: Use     get_cpu() instead of smp_processor_id() to avoid crash When CPU 0 is offline and intel_powerclamp is used     to inject idle, it generates kernel BUG: BUG: using smp_processor_id() in preemptible [00000000] code:
    bash/15687 caller is debug_smp_processor_id+0x17/0x20 CPU: 4 PID: 15687 Comm: bash Not tainted 5.19.0-rc7+     #57 Call Trace: <TASK> dump_stack_lvl+0x49/0x63 dump_stack+0x10/0x16 check_preemption_disabled+0xdd/0xe0     debug_smp_processor_id+0x17/0x20 powerclamp_set_cur_state+0x7f/0xf9 [intel_powerclamp] ... ... Here CPU 0     is the control CPU by default and changed to the current CPU, if CPU 0 offlined. This check has to be     performed under cpus_read_lock(), hence the above warning. Use get_cpu() instead of smp_processor_id() to     avoid this BUG. [ rjw: Subject edits ] (CVE-2022-50494)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
269377	Linux Distros 未修補的弱點：CVE-2023-53598	Nessus	Misc.	2025/10/8	2026/11/5	medium
360826	AlmaLinux 9.2 [TuxCare] 安全性更新：bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc 多個弱點（ALMALINUX9.2：CLSA-2026：1781347338）	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/19	high
360826	AlmaLinux 9.2 [TuxCare] 安全更新：bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / 等多个漏洞（ALMALINUX9.2：CLSA-2026：1781347338）	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/19	high
269377	Linux Distros 未修补的漏洞：CVE-2023-53598	Nessus	Misc.	2025/10/8	2026/11/5	medium
269377	Linux Distros のパッチ未適用の脆弱性: CVE-2023-53598	Nessus	Misc.	2025/10/8	2026/11/5	medium
360826	AlmaLinux 9.2 [TuxCare] セキュリティ更新プログラム:bpftool/kernel/kernel-64k/kernel-64k-core/kernel-64k-debug/etcの複数の脆弱性(ALMALINUX9.2:CLSA-2026:1781347338)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/19	high
280691	SUSE SLES15: Linux カーネルのセキュリティ更新 (SUSE-SU-2025:4320-1)	Nessus	SuSE Local Security Checks	2025/12/30	2026/9/29	high
269377	Linux Distros Unpatched Vulnerability : CVE-2023-53598	Nessus	Misc.	2025/10/8	2026/11/5	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	2021/7/22	2026/11/2	high
280691	SUSE SLES15 : Security update for the Linux Kernel (SUSE-SU-2025:4320-1)	Nessus	SuSE Local Security Checks	2025/12/30	2026/9/29	high
360826	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1781347338)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/19	high

检测

插件搜索

medium

high

high

medium

medium

high

high

medium

high

high

high