远程 Debian 12 主机上存在安装的程序包该程序包受到 dsa-5973 公告中提及的多个漏洞的影响。

    - ------------------------------------------------- ------------------------ Debian 安全公告 DSA-5973-1 security@debian.org https://www.debian.org/security/Salvatore Bonaccorso 2025 年 8 月 12 日 https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    程序包：linux CVE ID：CVE-2024-36350 CVE-2024-36357 CVE-2024-36913 CVE-2024-41013 CVE-2024-56758 CVE-2024-57883 CVE-2025-21816 CVE-2025-22119 CVE-2025-27558 CVE-2025-37958 CVE-2025-38000 CVE-2025-38001 CVE-2025-38003 CVE-2025-38004 CVE-2025-38031 CVE-2025-38034 CVE-2025-38035 CVE-2025-38037 CVE-2025-38040 CVE-2025-38043 CVE-2025-38044 CVE-2025-38048 CVE-2025-38051 CVE-2025-38052 CVE-2025-38058 CVE-2025-38061 CVE-2025-38062 CVE-2025-38063 CVE-2025-38065 CVE-2025-38066 CVE-2025-38067 CVE-2025-38068 CVE-2025-38071 CVE-2025-38072 CVE-2025-38074 CVE-2025-38075 CVE-2025-38077 CVE-2025-38078 CVE-2025-38079 CVE-2025-38083 CVE-2025-38084 CVE-2025-38085 CVE-2025-38086 CVE-2025-38088 CVE-2025-38090 CVE-2025-38097 CVE-2025-38100 CVE-2025-38102 CVE-2025-38103 CVE-2025-38107 CVE-2025-38108 CVE-2025-38111 CVE-2025-38112 CVE-2025-38113 CVE-2025-38115 CVE-2025-38118 CVE-2025-38119 CVE-2025-38120 CVE-2025-38122 CVE-2025-38124 CVE-2025-38126 CVE-2025-38131 CVE-2025-38135 CVE-2025-38136 CVE-2025-38138 CVE-2025-38142 CVE-2025-38143 CVE-2025-38145 CVE-2025-38146 CVE-2025-38147 CVE-2025-38148 CVE-2025-38151 CVE-2025-38153 CVE-2025-38154 CVE-2025-38157 CVE-2025-38158 CVE-2025-38159 CVE-2025-38160 CVE-2025-38161 CVE-2025-38163 CVE-2025-38165 CVE-2025-38166 CVE-2025-38167 CVE-2025-38170 CVE-2025-38173 CVE-2025-38174 CVE-2025-38180 CVE-2025-38181 CVE-2025-38183 CVE-2025-38184 CVE-2025-38185 CVE-2025-38190 CVE-2025-38191 CVE-2025-38193 CVE-2025-38194 CVE-2025-38197 CVE-2025-38198 CVE-2025-38200 CVE-2025-38202 CVE-2025-38211 CVE-2025-38212 CVE-2025-38214 CVE-2025-38215 CVE-2025-38218 CVE-2025-38219 CVE-2025-38222 CVE-2025-38225 CVE-2025-38226 CVE-2025-38227 CVE-2025-38229 CVE-2025-38230 CVE-2025-38231 CVE-2025-38236 CVE-2025-38239 CVE-2025-38245 CVE-2025-38249 CVE-2025-38251 CVE-2025-38257 CVE-2025-38259 CVE-2025-38260 CVE-2025-38262 CVE-2025-38263 CVE-2025-38273 CVE-2025-38275 CVE-2025-38277 CVE-2025-38280 CVE-2025-38282 CVE-2025-38285 CVE-2025-38286 CVE-2025-38293 CVE-2025-38298 CVE-2025-38300 CVE-2025-38304 CVE-2025-38305 CVE-2025-38310 CVE-2025-38312 CVE-2025-38313 CVE-2025-38319 CVE-2025-38320 CVE-2025-38323 CVE-2025-38324 CVE-2025-38326 CVE-2025-38328 CVE-2025-38331 CVE-2025-38332 CVE-2025-38334 CVE-2025-38336 CVE-2025-38337 CVE-2025-38342 CVE-2025-38344 CVE-2025-38345 CVE-2025-38346 CVE-2025-38348 CVE-2025-38350 CVE-2025-38352 CVE-2025-38354 CVE-2025-38362 CVE-2025-38363 CVE-2025-38364 CVE-2025-38365 CVE-2025-38371 CVE-2025-38375 CVE-2025-38377 CVE-2025-38380 CVE-2025-38382 CVE-2025-38384 CVE-2025-38385 CVE-2025-38386 CVE-2025-38387 CVE-2025-38389 CVE-2025-38391 CVE-2025-38393 CVE-2025-38395 CVE-2025-38396 CVE-2025-38399 CVE-2025-38400 CVE-2025-38401 CVE-2025-38403 CVE-2025-38404 CVE-2025-38406 CVE-2025-38409 CVE-2025-38410 CVE-2025-38412 CVE-2025-38415 CVE-2025-38416 CVE-2025-38418 CVE-2025-38419 CVE-2025-38420 CVE-2025-38422 CVE-2025-38424 CVE-2025-38425 CVE-2025-38428 CVE-2025-38430 CVE-2025-38437 CVE-2025-38439 CVE-2025-38441 CVE-2025-38443 CVE-2025-38444 CVE-2025-38445 CVE-2025-38448 CVE-2025-38451 CVE-2025-38455 CVE-2025-38456 CVE-2025-38457 CVE-2025-38458 CVE-2025-38459 CVE-2025-38460 CVE-2025-38461 CVE-2025-38462 CVE-2025-38464 CVE-2025-38465 CVE-2025-38466 CVE-2025-38467 CVE-2025-38468 CVE-2025-38470 CVE-2025-38471 CVE-2025-38472 CVE-2025-38473 CVE-2025-38474 CVE-2025-38476 CVE-2025-38477 CVE-2025-38478 CVE-2025-38480 CVE-2025-38481 CVE-2025-38482 CVE-2025-38483 CVE-2025-38485 CVE-2025-38487 CVE-2025-38488 CVE-2025-38494 CVE-2025-38495 CVE-2025-38497 CVE-2025-38498 CVE-2025-38499

    在 Linux 内核中发现多个可能导致权限升级、拒绝服务或信息泄漏的漏洞。

    对于旧稳定发行版本 (bookbird)这些问题已在版本 6.1.147-1中修复。

    建议您升级 linux 程序包。

    如需了解 linux 的详细安全状态，请参阅其安全跟踪页面：
    https://security-tracker.debian.org/tracker/linux

    有关 Debian 安全公告、如何将这些更新应用到系统以及常见问题解答的更多信息，请访问以下网址：https://www.debian.org/security/

    邮件列表：debian-security-announce@lists.debian.org

Tenable 已直接从 Debian 安全公告中提取上述描述块。

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

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

  - i2c/designware: Fix an initialization issue The i2c_dw_xfer_init() function requires msgs and     msg_write_idx from the dev context to be initialized. amd_i2c_dw_xfer_quirk() inits msgs and msgs_num, but     not msg_write_idx. This could allow an out of bounds access (of msgs). Initialize msg_write_idx before     calling i2c_dw_xfer_init(). (CVE-2025-38380)

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

The remote CentOS Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the kernel-5.14.0-604.el9 build changelog.

  - In the Linux kernel, the following vulnerability has been resolved: idpf: fix adapter NULL pointer     dereference on reboot With SRIOV enabled, idpf ends up calling into idpf_remove() twice. First via     idpf_shutdown() and then again when idpf_remove() calls into sriov_disable(), because the VF devices use     the idpf driver, hence the same remove routine. When that happens, it is possible for the adapter to be     NULL from the first call to idpf_remove(), leading to a NULL pointer dereference. echo 1 >     /sys/class/net/<netif>/device/sriov_numvfs reboot BUG: kernel NULL pointer dereference, address:
    0000000000000020 ... RIP: 0010:idpf_remove+0x22/0x1f0 [idpf] ... ? idpf_remove+0x22/0x1f0 [idpf] ?     idpf_remove+0x1e4/0x1f0 [idpf] pci_device_remove+0x3f/0xb0 device_release_driver_internal+0x19f/0x200     pci_stop_bus_device+0x6d/0x90 pci_stop_and_remove_bus_device+0x12/0x20 pci_iov_remove_virtfn+0xbe/0x120     sriov_disable+0x34/0xe0 idpf_sriov_configure+0x58/0x140 [idpf] idpf_remove+0x1b9/0x1f0 [idpf]     idpf_shutdown+0x12/0x30 [idpf] pci_device_shutdown+0x35/0x60 device_shutdown+0x156/0x200 ... Replace the     direct idpf_remove() call in idpf_shutdown() with idpf_vc_core_deinit() and idpf_deinit_dflt_mbx(), which     perform the bulk of the cleanup, such as stopping the init task, freeing IRQs, destroying the vports and     freeing the mailbox. This avoids the calls to sriov_disable() in addition to a small netdev cleanup, and     destroying workqueues, which don't seem to be required on shutdown. (CVE-2025-22065)

  - In the Linux kernel, the following vulnerability has been resolved: idpf: convert workqueues to unbound     When a workqueue is created with `WQ_UNBOUND`, its work items are served by special worker-pools, whose     host workers are not bound to any specific CPU. In the default configuration (i.e. when     `queue_delayed_work` and friends do not specify which CPU to run the work item on), `WQ_UNBOUND` allows     the work item to be executed on any CPU in the same node of the CPU it was enqueued on. While this     solution potentially sacrifices locality, it avoids contention with other processes that might dominate     the CPU time of the processor the work item was scheduled on. This is not just a theoretical problem: in a     particular scenario misconfigured process was hogging most of the time from CPU0, leaving less than 0.5%     of its CPU time to the kworker. The IDPF workqueues that were using the kworker on CPU0 suffered large     completion delays as a result, causing performance degradation, timeouts and eventual system crash. * I     have also run a manual test to gauge the performance improvement. The test consists of an antagonist     process (`./stress --cpu 2`) consuming as much of CPU 0 as possible. This process is run under `taskset     01` to bind it to CPU0, and its priority is changed with `chrt -pQ 9900 10000 ${pid}` and `renice -n -20     ${pid}` after start. Then, the IDPF driver is forced to prefer CPU0 by editing all calls to     `queue_delayed_work`, `mod_delayed_work`, etc... to use CPU 0. Finally, `ktraces` for the workqueue events     are collected. Without the current patch, the antagonist process can force arbitrary delays between     `workqueue_queue_work` and `workqueue_execute_start`, that in my tests were as high as `30ms`. With the     current patch applied, the workqueue can be migrated to another unloaded CPU in the same node, and,     keeping everything else equal, the maximum delay I could see was `6us`. (CVE-2024-58057)

  - In the Linux kernel, the following vulnerability has been resolved: idpf: fix checksums set in     idpf_rx_rsc() idpf_rx_rsc() uses skb_transport_offset(skb) while the transport header is not set yet. This     triggers the following warning for CONFIG_DEBUG_NET=y builds.
    DEBUG_NET_WARN_ON_ONCE(!skb_transport_header_was_set(skb)) [ 69.261620] WARNING: CPU: 7 PID: 0 at     ./include/linux/skbuff.h:3020 idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261629]     Modules linked in: vfat fat dummy bridge intel_uncore_frequency_tpmi intel_uncore_frequency_common     intel_vsec_tpmi idpf intel_vsec cdc_ncm cdc_eem cdc_ether usbnet mii xhci_pci xhci_hcd ehci_pci ehci_hcd     libeth [ 69.261644] CPU: 7 UID: 0 PID: 0 Comm: swapper/7 Tainted: G S W 6.14.0-smp-DEV #1697 [ 69.261648]     Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN [ 69.261650] RIP: 0010:idpf_vport_splitq_napi_poll     (include/linux/skbuff.h:3020) idpf [ 69.261677] ? __warn (kernel/panic.c:242 kernel/panic.c:748) [     69.261682] ? idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261687] ? report_bug     (lib/bug.c:?) [ 69.261690] ? handle_bug (arch/x86/kernel/traps.c:285) [ 69.261694] ? exc_invalid_op     (arch/x86/kernel/traps.c:309) [ 69.261697] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [     69.261700] ? __pfx_idpf_vport_splitq_napi_poll (drivers/net/ethernet/intel/idpf/idpf_txrx.c:4011) idpf [     69.261704] ? idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261708] ?     idpf_vport_splitq_napi_poll (drivers/net/ethernet/intel/idpf/idpf_txrx.c:3072) idpf [ 69.261712]
    __napi_poll (net/core/dev.c:7194) [ 69.261716] net_rx_action (net/core/dev.c:7265) [ 69.261718] ?
    __qdisc_run (net/sched/sch_generic.c:293) [ 69.261721] ? sched_clock (arch/x86/include/asm/preempt.h:84     arch/x86/kernel/tsc.c:288) [ 69.261726] handle_softirqs (kernel/softirq.c:561) (CVE-2025-21890)

  - In the Linux kernel, the following vulnerability has been resolved: idpf: check error for     register_netdev() on init Current init logic ignores the error code from register_netdev(), which will     cause WARN_ON() on attempt to unregister it, if there was one, and there is no info for the user that the     creation of the netdev failed. WARNING: CPU: 89 PID: 6902 at net/core/dev.c:11512     unregister_netdevice_many_notify+0x211/0x1a10 ... [ 3707.563641] unregister_netdev+0x1c/0x30 [     3707.563656] idpf_vport_dealloc+0x5cf/0xce0 [idpf] [ 3707.563684] idpf_deinit_task+0xef/0x160 [idpf] [     3707.563712] idpf_vc_core_deinit+0x84/0x320 [idpf] [ 3707.563739] idpf_remove+0xbf/0x780 [idpf] [     3707.563769] pci_device_remove+0xab/0x1e0 [ 3707.563786] device_release_driver_internal+0x371/0x530 [     3707.563803] driver_detach+0xbf/0x180 [ 3707.563816] bus_remove_driver+0x11b/0x2a0 [ 3707.563829]     pci_unregister_driver+0x2a/0x250 Introduce an error check and log the vport number and error code. On     removal make sure to check VPORT_REG_NETDEV flag prior to calling unregister and free on the netdev. Add     local variables for idx, vport_config and netdev for readability. (CVE-2025-22116)

  - In the Linux kernel, the following vulnerability has been resolved: idpf: fix null-ptr-deref in     idpf_features_check idpf_features_check is used to validate the TX packet. skb header length is compared     with the hardware supported value received from the device control plane. The value is stored in the     adapter structure and to access it, vport pointer is used. During reset all the vports are released and     the vport pointer that the netdev private structure points to is NULL. To avoid null-ptr-deref, store the     max header length value in netdev private structure. This also helps to cache the value and avoid     accessing adapter pointer in hot path. BUG: kernel NULL pointer dereference, address: 0000000000000068 ...
    RIP: 0010:idpf_features_check+0x6d/0xe0 [idpf] Call Trace: <TASK> ? __die+0x23/0x70 ?     page_fault_oops+0x154/0x520 ? exc_page_fault+0x76/0x190 ? asm_exc_page_fault+0x26/0x30 ?     idpf_features_check+0x6d/0xe0 [idpf] netif_skb_features+0x88/0x310 validate_xmit_skb+0x2a/0x2b0     validate_xmit_skb_list+0x4c/0x70 sch_direct_xmit+0x19d/0x3a0 __dev_queue_xmit+0xb74/0xe70 ...
    (CVE-2025-38053)

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

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

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

    Security Fix(es):

    * kernel: media: uvcvideo: Remove dangling pointers (CVE-2024-58002)

    * kernel: padata: fix UAF in padata_reorder (CVE-2025-21727)

    * kernel: media: uvcvideo: Fix double free in error path (CVE-2024-57980)

    * kernel: HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() (CVE-2025-21928)

    * kernel: sched/fair: Fix potential memory corruption in child_cfs_rq_on_list (CVE-2025-21919)

    * kernel: ext4: fix off-by-one error in do_split (CVE-2025-23150)

    * kernel: misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() (CVE-2022-49788)

    * kernel: net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done (CVE-2025-38052)

    * kernel: ext4: avoid resizing to a partial cluster size (CVE-2022-50020)

    * kernel: drivers:md:fix a potential use-after-free bug (CVE-2022-50022)

    * kernel: net: ch9200: fix uninitialised access during mii_nway_restart (CVE-2025-38086)

    * kernel: i2c/designware: Fix an initialization issue (CVE-2025-38380)

    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.

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 remote Debian 12 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-5973 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-5973-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     August 12, 2025                       https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : linux     CVE ID         : CVE-2024-36350 CVE-2024-36357 CVE-2024-36913 CVE-2024-41013                      CVE-2024-56758 CVE-2024-57883 CVE-2025-21816 CVE-2025-22119                      CVE-2025-27558 CVE-2025-37958 CVE-2025-38000 CVE-2025-38001                      CVE-2025-38003 CVE-2025-38004 CVE-2025-38031 CVE-2025-38034                      CVE-2025-38035 CVE-2025-38037 CVE-2025-38040 CVE-2025-38043                      CVE-2025-38044 CVE-2025-38048 CVE-2025-38051 CVE-2025-38052                      CVE-2025-38058 CVE-2025-38061 CVE-2025-38062 CVE-2025-38063                      CVE-2025-38065 CVE-2025-38066 CVE-2025-38067 CVE-2025-38068                      CVE-2025-38071 CVE-2025-38072 CVE-2025-38074 CVE-2025-38075                      CVE-2025-38077 CVE-2025-38078 CVE-2025-38079 CVE-2025-38083                      CVE-2025-38084 CVE-2025-38085 CVE-2025-38086 CVE-2025-38088                      CVE-2025-38090 CVE-2025-38097 CVE-2025-38100 CVE-2025-38102                      CVE-2025-38103 CVE-2025-38107 CVE-2025-38108 CVE-2025-38111                      CVE-2025-38112 CVE-2025-38113 CVE-2025-38115 CVE-2025-38118                      CVE-2025-38119 CVE-2025-38120 CVE-2025-38122 CVE-2025-38124                      CVE-2025-38126 CVE-2025-38131 CVE-2025-38135 CVE-2025-38136                      CVE-2025-38138 CVE-2025-38142 CVE-2025-38143 CVE-2025-38145                      CVE-2025-38146 CVE-2025-38147 CVE-2025-38148 CVE-2025-38151                      CVE-2025-38153 CVE-2025-38154 CVE-2025-38157 CVE-2025-38158                      CVE-2025-38159 CVE-2025-38160 CVE-2025-38161 CVE-2025-38163                      CVE-2025-38165 CVE-2025-38166 CVE-2025-38167 CVE-2025-38170                      CVE-2025-38173 CVE-2025-38174 CVE-2025-38180 CVE-2025-38181                      CVE-2025-38183 CVE-2025-38184 CVE-2025-38185 CVE-2025-38190                      CVE-2025-38191 CVE-2025-38193 CVE-2025-38194 CVE-2025-38197                      CVE-2025-38198 CVE-2025-38200 CVE-2025-38202 CVE-2025-38211                      CVE-2025-38212 CVE-2025-38214 CVE-2025-38215 CVE-2025-38218                      CVE-2025-38219 CVE-2025-38222 CVE-2025-38225 CVE-2025-38226                      CVE-2025-38227 CVE-2025-38229 CVE-2025-38230 CVE-2025-38231                      CVE-2025-38236 CVE-2025-38239 CVE-2025-38245 CVE-2025-38249                      CVE-2025-38251 CVE-2025-38257 CVE-2025-38259 CVE-2025-38260                      CVE-2025-38262 CVE-2025-38263 CVE-2025-38273 CVE-2025-38275                      CVE-2025-38277 CVE-2025-38280 CVE-2025-38282 CVE-2025-38285                      CVE-2025-38286 CVE-2025-38293 CVE-2025-38298 CVE-2025-38300                      CVE-2025-38304 CVE-2025-38305 CVE-2025-38310 CVE-2025-38312                      CVE-2025-38313 CVE-2025-38319 CVE-2025-38320 CVE-2025-38323                      CVE-2025-38324 CVE-2025-38326 CVE-2025-38328 CVE-2025-38331                      CVE-2025-38332 CVE-2025-38334 CVE-2025-38336 CVE-2025-38337                      CVE-2025-38342 CVE-2025-38344 CVE-2025-38345 CVE-2025-38346                      CVE-2025-38348 CVE-2025-38350 CVE-2025-38352 CVE-2025-38354                      CVE-2025-38362 CVE-2025-38363 CVE-2025-38364 CVE-2025-38365                      CVE-2025-38371 CVE-2025-38375 CVE-2025-38377 CVE-2025-38380                      CVE-2025-38382 CVE-2025-38384 CVE-2025-38385 CVE-2025-38386                      CVE-2025-38387 CVE-2025-38389 CVE-2025-38391 CVE-2025-38393                      CVE-2025-38395 CVE-2025-38396 CVE-2025-38399 CVE-2025-38400                      CVE-2025-38401 CVE-2025-38403 CVE-2025-38404 CVE-2025-38406                      CVE-2025-38409 CVE-2025-38410 CVE-2025-38412 CVE-2025-38415                      CVE-2025-38416 CVE-2025-38418 CVE-2025-38419 CVE-2025-38420                      CVE-2025-38422 CVE-2025-38424 CVE-2025-38425 CVE-2025-38428                      CVE-2025-38430 CVE-2025-38437 CVE-2025-38439 CVE-2025-38441                      CVE-2025-38443 CVE-2025-38444 CVE-2025-38445 CVE-2025-38448                      CVE-2025-38451 CVE-2025-38455 CVE-2025-38456 CVE-2025-38457                      CVE-2025-38458 CVE-2025-38459 CVE-2025-38460 CVE-2025-38461                      CVE-2025-38462 CVE-2025-38464 CVE-2025-38465 CVE-2025-38466                      CVE-2025-38467 CVE-2025-38468 CVE-2025-38470 CVE-2025-38471                      CVE-2025-38472 CVE-2025-38473 CVE-2025-38474 CVE-2025-38476                      CVE-2025-38477 CVE-2025-38478 CVE-2025-38480 CVE-2025-38481                      CVE-2025-38482 CVE-2025-38483 CVE-2025-38485 CVE-2025-38487                      CVE-2025-38488 CVE-2025-38494 CVE-2025-38495 CVE-2025-38497                      CVE-2025-38498 CVE-2025-38499

    Several vulnerabilities have been discovered in the Linux kernel that     may lead to a privilege escalation, denial of service or information     leaks.

    For the oldstable distribution (bookworm), these problems have been fixed     in version 6.1.147-1.

    We recommend that you upgrade your linux packages.

    For the detailed security status of linux please refer to its security     tracker page at:
    https://security-tracker.debian.org/tracker/linux

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian security advisory.

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

リモートの CentOS Linux 9 ホストには、kernel-5.14.0-604.el9 ビルド変更ログで言及されているように、複数の脆弱性の影響を受けるパッケージがインストールされています。

  - Linux カーネルでは、以下の脆弱性が解決されています: idpf: fix adapter NULL pointer dereference on reboot With SRIOV enabled, idpf ends up calling into idpf_remove() twice. First via idpf_shutdown() and then again when idpf_remove() calls into sriov_disable(), because the VF devices use the idpf driver, hence the same remove routine. When that happens, it is possible for the adapter to be NULL from the first call to idpf_remove(), leading to a NULL pointer dereference. echo 1 > /sys/class/net/<netif>/device/sriov_numvfs reboot BUG: kernel NULL pointer dereference, address:
    0000000000000020 ... RIP: 0010:idpf_remove+0x22/0x1f0 [idpf] ... ? idpf_remove+0x22/0x1f0 [idpf] ? idpf_remove+0x1e4/0x1f0 [idpf] pci_device_remove+0x3f/0xb0 device_release_driver_internal+0x19f/0x200 pci_stop_bus_device+0x6d/0x90 pci_stop_and_remove_bus_device+0x12/0x20 pci_iov_remove_virtfn+0xbe/0x120 sriov_disable+0x34/0xe0 idpf_sriov_configure+0x58/0x140 [idpf] idpf_remove+0x1b9/0x1f0 [idpf] idpf_shutdown+0x12/0x30 [idpf] pci_device_shutdown+0x35/0x60 device_shutdown+0x156/0x200 ... Replace the direct idpf_remove() call in idpf_shutdown() with idpf_vc_core_deinit() and idpf_deinit_dflt_mbx(), which perform the bulk of the cleanup, such as stopping the init task, freeing IRQs, destroying the vports and freeing the mailbox. This avoids the calls to sriov_disable() in addition to a small netdev cleanup, and destroying workqueues, which don't seem to be required on shutdown. (CVE-2025-22065)

  - Linux カーネルでは、以下の脆弱性が解決されています: idpf: convert workqueues to unbound When a workqueue is created with `WQ_UNBOUND`, its work items are served by special worker-pools, whose host workers are not bound to any specific CPU. In the default configuration (i.e. when `queue_delayed_work` and friends do not specify which CPU to run the work item on), `WQ_UNBOUND` allows the work item to be executed on any CPU in the same node of the CPU it was enqueued on. While this solution potentially sacrifices locality, it avoids contention with other processes that might dominate the CPU time of the processor the work item was scheduled on. This is not just a theoretical problem: in a particular scenario misconfigured process was hogging most of the time from CPU0, leaving less than 0.5% of its CPU time to the kworker. The IDPF workqueues that were using the kworker on CPU0 suffered large completion delays as a result, causing performance degradation, timeouts and eventual system crash. * I have also run a manual test to gauge the performance improvement. The test consists of an antagonist process (`./stress --cpu 2`) consuming as much of CPU 0 as possible. This process is run under `taskset 01` to bind it to CPU0, and its priority is changed with `chrt -pQ 9900 10000 ${pid}` and `renice -n -20 ${pid}` after start. Then, the IDPF driver is forced to prefer CPU0 by editing all calls to `queue_delayed_work`, `mod_delayed_work`, etc... to use CPU 0. Finally, `ktraces` for the workqueue events are collected. Without the current patch, the antagonist process can force arbitrary delays between `workqueue_queue_work` and `workqueue_execute_start`, that in my tests were as high as `30ms`. With the current patch applied, the workqueue can be migrated to another unloaded CPU in the same node, and, keeping everything else equal, the maximum delay I could see was `6us`. (CVE-2024-58057)

  - Linux カーネルでは、以下の脆弱性が解決されています: idpf: fix checksums set in idpf_rx_rsc() idpf_rx_rsc() uses skb_transport_offset(skb) while the transport header is not set yet. This triggers the following warning for CONFIG_DEBUG_NET=y builds.
    DEBUG_NET_WARN_ON_ONCE(!skb_transport_header_was_set(skb)) [ 69.261620] WARNING: CPU: 7 PID: 0 at ./include/linux/skbuff.h:3020 idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261629] Modules linked in: vfat fat dummy bridge intel_uncore_frequency_tpmi intel_uncore_frequency_common intel_vsec_tpmi idpf intel_vsec cdc_ncm cdc_eem cdc_ether usbnet mii xhci_pci xhci_hcd ehci_pci ehci_hcd libeth [ 69.261644] CPU: 7 UID: 0 PID: 0 Comm: swapper/7 Tainted: G S W 6.14.0-smp-DEV #1697 [ 69.261648] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN [ 69.261650] RIP: 0010:idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261677] ? __warn (kernel/panic.c:242 kernel/panic.c:748) [69.261682] ? idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261687] ? report_bug (lib/bug.c:?) [ 69.261690] ? handle_bug (arch/x86/kernel/traps.c:285) [ 69.261694] ? exc_invalid_op (arch/x86/kernel/traps.c:309) [ 69.261697] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [69.261700] ? __pfx_idpf_vport_splitq_napi_poll (drivers/net/ethernet/intel/idpf/idpf_txrx.c:4011) idpf [69.261704] ? idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261708] ? idpf_vport_splitq_napi_poll (drivers/net/ethernet/intel/idpf/idpf_txrx.c:3072) idpf [ 69.261712]
    __napi_poll (net/core/dev.c:7194) [ 69.261716] net_rx_action (net/core/dev.c:7265) [ 69.261718] ?
    __qdisc_run (net/sched/sch_generic.c:293) [ 69.261721] ? sched_clock (arch/x86/include/asm/preempt.h:84 arch/x86/kernel/tsc.c:288) [ 69.261726] handle_softirqs (kernel/softirq.c:561) (CVE-2025-21890)

  - Linux カーネルでは、以下の脆弱性が解決されています: idpf: check error for register_netdev() on init Current init logic ignores the error code from register_netdev(), which will cause WARN_ON() on attempt to unregister it, if there was one, and there is no info for the user that the creation of the netdev failed. WARNING: CPU: 89 PID: 6902 at net/core/dev.c:11512 unregister_netdevice_many_notify+0x211/0x1a10 ... [ 3707.563641] unregister_netdev+0x1c/0x30 [3707.563656] idpf_vport_dealloc+0x5cf/0xce0 [idpf] [ 3707.563684] idpf_deinit_task+0xef/0x160 [idpf] [3707.563712] idpf_vc_core_deinit+0x84/0x320 [idpf] [ 3707.563739] idpf_remove+0xbf/0x780 [idpf] [3707.563769] pci_device_remove+0xab/0x1e0 [ 3707.563786] device_release_driver_internal+0x371/0x530 [3707.563803] driver_detach+0xbf/0x180 [ 3707.563816] bus_remove_driver+0x11b/0x2a0 [ 3707.563829] pci_unregister_driver+0x2a/0x250 Introduce an error check and log the vport number and error code. On removal make sure to check VPORT_REG_NETDEV flag prior to calling unregister and free on the netdev. Add local variables for idx, vport_config and netdev for readability. (CVE-2025-22116)

  - Linux カーネルでは、以下の脆弱性が解決されています: idpf: fix null-ptr-deref in idpf_features_check idpf_features_check is used to validate the TX packet. skb header length is compared with the hardware supported value received from the device control plane. The value is stored in the adapter structure and to access it, vport pointer is used. During reset all the vports are released and the vport pointer that the netdev private structure points to is NULL. To avoid null-ptr-deref, store the max header length value in netdev private structure. This also helps to cache the value and avoid accessing adapter pointer in hot path. BUG: kernel NULL pointer dereference, address: 0000000000000068 ...
    RIP: 0010:idpf_features_check+0x6d/0xe0 [idpf] Call Trace: <TASK> ? __die+0x23/0x70 ? page_fault_oops+0x154/0x520 ? exc_page_fault+0x76/0x190 ? asm_exc_page_fault+0x26/0x30 ? idpf_features_check+0x6d/0xe0 [idpf] netif_skb_features+0x88/0x310 validate_xmit_skb+0x2a/0x2b0 validate_xmit_skb_list+0x4c/0x70 sch_direct_xmit+0x19d/0x3a0 __dev_queue_xmit+0xb74/0xe70 ...
    (CVE-2025-38053)

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

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

    カーネルパッケージには、Linux オペレーティングシステムのコアである Linux カーネルが含まれています。

    セキュリティ修正プログラム:

    * kernel: media: uvcvideo: ダングリングポインターを削除します (CVE-2024-58002)

    * kernel: padata: padata_reorder での UAF を修正します (CVE-2025-21727)

    * kernel: media: uvcvideo: エラーパス内の二重解放を修正します (CVE-2024-57980)。

    * kernel: HID: intel-ish-hid: ishtp_hid_remove() のメモリ解放後使用 (Use After Free) の問題を修正します (CVE-2025-21928)

    * kernel: sched/fair: child_cfs_rq_on_list のメモリ破損の可能性を修正 (CVE-2025-21919)

    * kernel: ext4: do_split の off-by-one エラーを修正 (CVE-2025-23150)

    * kernel: misc/vmw_vmci: vmci_host_do_receive_datagram() の情報漏洩を修正します (CVE-2022-49788)

    * kernel: net/tipc: tipc_aead_encrypt_done の slab-use-after-free 読み取りを修正します (CVE-2025-38052)

    * kernel: ext4: 部分的なクラスターサイズへのサイズ変更を回避します (CVE-2022-50020)

    * カーネルdriversmd潜在的な use-after-free バグを修正しますCVE-2022-50022

    * kernel: net: ch9200: mii_nway_restart 中の初期化されていないアクセスを修正します (CVE-2025-38086)

    * カーネルi2c/designware 初期化の問題を修正しますCVE-2025-38380

    影響、CVSS スコア、謝辞、その他の関連情報を含むセキュリティ問題の詳細については、「参照」セクションに記載されている CVE のページを参照してください。

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

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

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

  - i2c/designware初期化の問題を修正します。i2c_dw_xfer_init() 関数は、初期化するために dev コンテキストからの msgs および msg_write_idx を初期化する必要があります。 amd_i2c_dw_xfer_quirk() は msgs と msgs_num を初期化しますが、msg_write_idx は初期化しません。これにより、領域外アクセスmsgsが可能になる可能性があります。i2c_dw_xfer_init() を呼び出す前に msg_write_idx を初期化します。CVE-2025-38380

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

遠端 Debian 12 主機已安裝受到多個弱點影響的套件如 dsa-5973 公告中所提及。

    - ------------------------------------------------- ------------------------ Debian 安全性公告 DSA-5973-1 security@debian.org https://www.debian.org/security/Salvatore Bonaccorso 2025 年 8 月 12 日 https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    套件：linux CVE ID：CVE-2024-36350 CVE-2024-36357 CVE-2024-36913 CVE-2024-41013 CVE-2024-56758 CVE-2024-57883 CVE-2025-21816 CVE-2025-22119 CVE-2025-27558 CVE-2025-37958 CVE-2025-38000 CVE-2025-38001 CVE-2025-38003 CVE-2025-38004 CVE-2025-38031 CVE-2025-38034 CVE-2025-38035 CVE-2025-38037 CVE-2025-38040 CVE-2025-38043 CVE-2025-38044 CVE-2025-38048 CVE-2025-38051 CVE-2025-38052 CVE-2025-38058 CVE-2025-38061 CVE-2025-38062 CVE-2025-38063 CVE-2025-38065 CVE-2025-38066 CVE-2025-38067 CVE-2025-38068 CVE-2025-38071 CVE-2025-38072 CVE-2025-38074 CVE-2025-38075 CVE-2025-38077 CVE-2025-38078 CVE-2025-38079 CVE-2025-38083 CVE-2025-38084 CVE-2025-38085 CVE-2025-38086 CVE-2025-38088 CVE-2025-38090 CVE-2025-38097 CVE-2025-38100 CVE-2025-38102 CVE-2025-38103 CVE-2025-38107 CVE-2025-38108 CVE-2025-38111 CVE-2025-38112 CVE-2025-38113 CVE-2025-38115 CVE-2025-38118 CVE-2025-38119 CVE-2025-38120 CVE-2025-38122 CVE-2025-38124 CVE-2025-38126 CVE-2025-38131 CVE-2025-38135 CVE-2025-38136 CVE-2025-38138 CVE-2025-38142 CVE-2025-38143 CVE-2025-38145 CVE-2025-38146 CVE-2025-38147 CVE-2025-38148 CVE-2025-38151 CVE-2025-38153 CVE-2025-38154 CVE-2025-38157 CVE-2025-38158 CVE-2025-38159 CVE-2025-38160 CVE-2025-38161 CVE-2025-38163 CVE-2025-38165 CVE-2025-38166 CVE-2025-38167 CVE-2025-38170 CVE-2025-38173 CVE-2025-38174 CVE-2025-38180 CVE-2025-38181 CVE-2025-38183 CVE-2025-38184 CVE-2025-38185 CVE-2025-38190 CVE-2025-38191 CVE-2025-38193 CVE-2025-38194 CVE-2025-38197 CVE-2025-38198 CVE-2025-38200 CVE-2025-38202 CVE-2025-38211 CVE-2025-38212 CVE-2025-38214 CVE-2025-38215 CVE-2025-38218 CVE-2025-38219 CVE-2025-38222 CVE-2025-38225 CVE-2025-38226 CVE-2025-38227 CVE-2025-38229 CVE-2025-38230 CVE-2025-38231 CVE-2025-38236 CVE-2025-38239 CVE-2025-38245 CVE-2025-38249 CVE-2025-38251 CVE-2025-38257 CVE-2025-38259 CVE-2025-38260 CVE-2025-38262 CVE-2025-38263 CVE-2025-38273 CVE-2025-38275 CVE-2025-38277 CVE-2025-38280 CVE-2025-38282 CVE-2025-38285 CVE-2025-38286 CVE-2025-38293 CVE-2025-38298 CVE-2025-38300 CVE-2025-38304 CVE-2025-38305 CVE-2025-38310 CVE-2025-38312 CVE-2025-38313 CVE-2025-38319 CVE-2025-38320 CVE-2025-38323 CVE-2025-38324 CVE-2025-38326 CVE-2025-38328 CVE-2025-38331 CVE-2025-38332 CVE-2025-38334 CVE-2025-38336 CVE-2025-38337 CVE-2025-38342 CVE-2025-38344 CVE-2025-38345 CVE-2025-38346 CVE-2025-38348 CVE-2025-38350 CVE-2025-38352 CVE-2025-38354 CVE-2025-38362 CVE-2025-38363 CVE-2025-38364 CVE-2025-38365 CVE-2025-38371 CVE-2025-38375 CVE-2025-38377 CVE-2025-38380 CVE-2025-38382 CVE-2025-38384 CVE-2025-38385 CVE-2025-38386 CVE-2025-38387 CVE-2025-38389 CVE-2025-38391 CVE-2025-38393 CVE-2025-38395 CVE-2025-38396 CVE-2025-38399 CVE-2025-38400 CVE-2025-38401 CVE-2025-38403 CVE-2025-38404 CVE-2025-38406 CVE-2025-38409 CVE-2025-38410 CVE-2025-38412 CVE-2025-38415 CVE-2025-38416 CVE-2025-38418 CVE-2025-38419 CVE-2025-38420 CVE-2025-38422 CVE-2025-38424 CVE-2025-38425 CVE-2025-38428 CVE-2025-38430 CVE-2025-38437 CVE-2025-38439 CVE-2025-38441 CVE-2025-38443 CVE-2025-38444 CVE-2025-38445 CVE-2025-38448 CVE-2025-38451 CVE-2025-38455 CVE-2025-38456 CVE-2025-38457 CVE-2025-38458 CVE-2025-38459 CVE-2025-38460 CVE-2025-38461 CVE-2025-38462 CVE-2025-38464 CVE-2025-38465 CVE-2025-38466 CVE-2025-38467 CVE-2025-38468 CVE-2025-38470 CVE-2025-38471 CVE-2025-38472 CVE-2025-38473 CVE-2025-38474 CVE-2025-38476 CVE-2025-38477 CVE-2025-38478 CVE-2025-38480 CVE-2025-38481 CVE-2025-38482 CVE-2025-38483 CVE-2025-38485 CVE-2025-38487 CVE-2025-38488 CVE-2025-38494 CVE-2025-38495 CVE-2025-38497 CVE-2025-38498 CVE-2025-38499

    在 Linux 核心中發現數個弱點，這些弱點可能會導致特權提升、拒絕服務或資訊洩漏。

    針對舊的穩定發行版本 (book蠕蟲)這些問題已在 6.1.147-1版中修正。

    建議您升級 linux 套件。

    如需有關 linux 安全性狀態的詳細資訊，請參閱其安全追蹤頁面：
    https://security-tracker.debian.org/tracker/linux

    有關 Debian 安全公告、如何將這些更新套用至您的系統以及常見問題的詳細資訊，請參閱：https://www.debian.org/security/

    郵寄清單：debian-security-announce@lists.debian.org

Tenable 已直接從 Debian 安全公告擷取前置描述區塊。

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

リモートの Debian 12 ホストには、dsa-5973 アドバイザリで言及されているように、複数の脆弱性の影響を受けるパッケージがインストールされています。

    - -------------------------------------------------- -------------------------- Debian セキュリティアドバイザリ DSA-5973-1 security@debian.org https://www.debian.org/security/Salvatore Bonaccorso 2025 年 8 月 12 日 https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    パッケージ: linux CVE ID: CVE-2024-36350 CVE-2024-36357 CVE-2024-36913 CVE-2024-41013 CVE-2024-56758 CVE-2024-57883 CVE-2025-21816 CVE-2025-22119 CVE-2025-27558 CVE-2025-37958 CVE-2025-38000 CVE-2025-38001 CVE-2025-38003 CVE-2025-38004 CVE-2025-38031 CVE-2025-38034 CVE-2025-38035 CVE-2025-38037 CVE-2025-38040 CVE-2025-38043 CVE-2025-38044 CVE-2025-38048 CVE-2025-38051 CVE-2025-38052 CVE-2025-38058 CVE-2025-38061 CVE-2025-38062 CVE-2025-38063 CVE-2025-38065 CVE-2025-38066 CVE-2025-38067 CVE-2025-38068 CVE-2025-38071 CVE-2025-38072 CVE-2025-38074 CVE-2025-38075 CVE-2025-38077 CVE-2025-38078 CVE-2025-38079 CVE-2025-38083 CVE-2025-38084 CVE-2025-38085 CVE-2025-38086 CVE-2025-38088 CVE-2025-38090 CVE-2025-38097 CVE-2025-38100 CVE-2025-38102 CVE-2025-38103 CVE-2025-38107 CVE-2025-38108 CVE-2025-38111 CVE-2025-38112 CVE-2025-38113 CVE-2025-38115 CVE-2025-38118 CVE-2025-38119 CVE-2025-38120 CVE-2025-38122 CVE-2025-38124 CVE-2025-38126 CVE-2025-38131 CVE-2025-38135 CVE-2025-38136 CVE-2025-38138 CVE-2025-38142 CVE-2025-38143 CVE-2025-38145 CVE-2025-38146 CVE-2025-38147 CVE-2025-38148 CVE-2025-38151 CVE-2025-38153 CVE-2025-38154 CVE-2025-38157 CVE-2025-38158 CVE-2025-38159 CVE-2025-38160 CVE-2025-38161 CVE-2025-38163 CVE-2025-38165 CVE-2025-38166 CVE-2025-38167 CVE-2025-38170 CVE-2025-38173 CVE-2025-38174 CVE-2025-38180 CVE-2025-38181 CVE-2025-38183 CVE-2025-38184 CVE-2025-38185 CVE-2025-38190 CVE-2025-38191 CVE-2025-38193 CVE-2025-38194 CVE-2025-38197 CVE-2025-38198 CVE-2025-38200 CVE-2025-38202 CVE-2025-38211 CVE-2025-38212 CVE-2025-38214 CVE-2025-38215 CVE-2025-38218 CVE-2025-38219 CVE-2025-38222 CVE-2025-38225 CVE-2025-38226 CVE-2025-38227 CVE-2025-38229 CVE-2025-38230 CVE-2025-38231 CVE-2025-38236 CVE-2025-38239 CVE-2025-38245 CVE-2025-38249 CVE-2025-38251 CVE-2025-38257 CVE-2025-38259 CVE-2025-38260 CVE-2025-38262 CVE-2025-38263 CVE-2025-38273 CVE-2025-38275 CVE-2025-38277 CVE-2025-38280 CVE-2025-38282 CVE-2025-38285 CVE-2025-38286 CVE-2025-38293 CVE-2025-38298 CVE-2025-38300 CVE-2025-38304 CVE-2025-38305 CVE-2025-38310 CVE-2025-38312 CVE-2025-38313 CVE-2025-38319 CVE-2025-38320 CVE-2025-38323 CVE-2025-38324 CVE-2025-38326 CVE-2025-38328 CVE-2025-38331 CVE-2025-38332 CVE-2025-38334 CVE-2025-38336 CVE-2025-38337 CVE-2025-38342 CVE-2025-38344 CVE-2025-38345 CVE-2025-38346 CVE-2025-38348 CVE-2025-38350 CVE-2025-38352 CVE-2025-38354 CVE-2025-38362 CVE-2025-38363 CVE-2025-38364 CVE-2025-38365 CVE-2025-38371 CVE-2025-38375 CVE-2025-38377 CVE-2025-38380 CVE-2025-38382 CVE-2025-38384 CVE-2025-38385 CVE-2025-38386 CVE-2025-38387 CVE-2025-38389 CVE-2025-38391 CVE-2025-38393 CVE-2025-38395 CVE-2025-38396 CVE-2025-38399 CVE-2025-38400 CVE-2025-38401 CVE-2025-38403 CVE-2025-38404 CVE-2025-38406 CVE-2025-38409 CVE-2025-38410 CVE-2025-38412 CVE-2025-38415 CVE-2025-38416 CVE-2025-38418 CVE-2025-38419 CVE-2025-38420 CVE-2025-38422 CVE-2025-38424 CVE-2025-38425 CVE-2025-38428 CVE-2025-38430 CVE-2025-38437 CVE-2025-38439 CVE-2025-38441 CVE-2025-38443 CVE-2025-38444 CVE-2025-38445 CVE-2025-38448 CVE-2025-38451 CVE-2025-38455 CVE-2025-38456 CVE-2025-38457 CVE-2025-38458 CVE-2025-38459 CVE-2025-38460 CVE-2025-38461 CVE-2025-38462 CVE-2025-38464 CVE-2025-38465 CVE-2025-38466 CVE-2025-38467 CVE-2025-38468 CVE-2025-38470 CVE-2025-38471 CVE-2025-38472 CVE-2025-38473 CVE-2025-38474 CVE-2025-38476 CVE-2025-38477 CVE-2025-38478 CVE-2025-38480 CVE-2025-38481 CVE-2025-38482 CVE-2025-38483 CVE-2025-38485 CVE-2025-38487 CVE-2025-38488 CVE-2025-38494 CVE-2025-38495 CVE-2025-38497 CVE-2025-38498 CVE-2025-38499

    Linux カーネルに、権限昇格、サービス拒否、または情報漏洩を引き起こす可能性がある、複数の脆弱性が発見されました。

    旧安定版oldstableディストリビューションbookword では、これらの問題はバージョン 6.1.147-1で修正されました。

    お使いの linux パッケージをアップグレードすることを推奨します。

    linux の詳細なセキュリティステータスについては、そのセキュリティトラッカーページを参照してください。
    https://security-tracker.debian.org/tracker/linux

    Debian セキュリティアドバイザリに関する詳細、これらの更新をシステムに適用する方法、およびよくある質問については、こちらを参照してください。https://www.debian.org/security/

    メーリングリスト: debian-security-announce@lists.debian.org

Tenable は、前述の説明ブロックを Debian セキュリティアドバイザリから直接抽出しました。

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

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

  - i2c/designware修正一個初始化問題。i2c_dw_xfer_init() 函式需要初始化來自 dev 內容的 msgs 和 msg_write_idx。 amd_i2c_dw_xfer_quirk() 初始化 msgs 和 msgs_num但不是 msg_write_idx。這可允許 (訊息) 超出邊界存取。在呼叫 i2c_dw_xfer_init() 之前初始化 msg_write_idx。 (CVE-2025-38380)

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

遠端 CentOS Linux 9 主機已安裝受到多個弱點影響的套件如 kernel-5.14.0-604.el9 版本變更記錄中所提及。

  - 已解決 Linux 核心中的下列弱點：idpf: fix adapter NULL pointer dereference on reboot With SRIOV enabled, idpf ends up calling into idpf_remove() twice. First via idpf_shutdown() and then again when idpf_remove() calls into sriov_disable(), because the VF devices use the idpf driver, hence the same remove routine. When that happens, it is possible for the adapter to be NULL from the first call to idpf_remove(), leading to a NULL pointer dereference. echo 1 > /sys/class/net/<netif>/device/sriov_numvfs reboot BUG: kernel NULL pointer dereference, address:
    0000000000000020 ... RIP: 0010:idpf_remove+0x22/0x1f0 [idpf] ... ? idpf_remove+0x22/0x1f0 [idpf] ? idpf_remove+0x1e4/0x1f0 [idpf] pci_device_remove+0x3f/0xb0 device_release_driver_internal+0x19f/0x200 pci_stop_bus_device+0x6d/0x90 pci_stop_and_remove_bus_device+0x12/0x20 pci_iov_remove_virtfn+0xbe/0x120 sriov_disable+0x34/0xe0 idpf_sriov_configure+0x58/0x140 [idpf] idpf_remove+0x1b9/0x1f0 [idpf] idpf_shutdown+0x12/0x30 [idpf] pci_device_shutdown+0x35/0x60 device_shutdown+0x156/0x200 ... Replace the direct idpf_remove() call in idpf_shutdown() with idpf_vc_core_deinit() and idpf_deinit_dflt_mbx(), which perform the bulk of the cleanup, such as stopping the init task, freeing IRQs, destroying the vports and freeing the mailbox. This avoids the calls to sriov_disable() in addition to a small netdev cleanup, and destroying workqueues, which don't seem to be required on shutdown. (CVE-2025-22065)

  - 已解決 Linux 核心中的下列弱點：idpf: convert workqueues to unbound When a workqueue is created with `WQ_UNBOUND`, its work items are served by special worker-pools, whose host workers are not bound to any specific CPU. In the default configuration (i.e. when `queue_delayed_work` and friends do not specify which CPU to run the work item on), `WQ_UNBOUND` allows the work item to be executed on any CPU in the same node of the CPU it was enqueued on. While this solution potentially sacrifices locality, it avoids contention with other processes that might dominate the CPU time of the processor the work item was scheduled on. This is not just a theoretical problem: in a particular scenario misconfigured process was hogging most of the time from CPU0, leaving less than 0.5% of its CPU time to the kworker. The IDPF workqueues that were using the kworker on CPU0 suffered large completion delays as a result, causing performance degradation, timeouts and eventual system crash. * I have also run a manual test to gauge the performance improvement. The test consists of an antagonist process (`./stress --cpu 2`) consuming as much of CPU 0 as possible. This process is run under `taskset 01` to bind it to CPU0, and its priority is changed with `chrt -pQ 9900 10000 ${pid}` and `renice -n -20 ${pid}` after start. Then, the IDPF driver is forced to prefer CPU0 by editing all calls to `queue_delayed_work`, `mod_delayed_work`, etc... to use CPU 0. Finally, `ktraces` for the workqueue events are collected. Without the current patch, the antagonist process can force arbitrary delays between `workqueue_queue_work` and `workqueue_execute_start`, that in my tests were as high as `30ms`. With the current patch applied, the workqueue can be migrated to another unloaded CPU in the same node, and, keeping everything else equal, the maximum delay I could see was `6us`. (CVE-2024-58057)

  - 已解決 Linux 核心中的下列弱點：idpf: fix checksums set in idpf_rx_rsc() idpf_rx_rsc() uses skb_transport_offset(skb) while the transport header is not set yet. This triggers the following warning for CONFIG_DEBUG_NET=y builds.
    DEBUG_NET_WARN_ON_ONCE(!skb_transport_header_was_set(skb)) [ 69.261620] WARNING: CPU: 7 PID: 0 at ./include/linux/skbuff.h:3020 idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261629] Modules linked in: vfat fat dummy bridge intel_uncore_frequency_tpmi intel_uncore_frequency_common intel_vsec_tpmi idpf intel_vsec cdc_ncm cdc_eem cdc_ether usbnet mii xhci_pci xhci_hcd ehci_pci ehci_hcd libeth [ 69.261644] CPU: 7 UID: 0 PID: 0 Comm: swapper/7 Tainted: G S W 6.14.0-smp-DEV #1697 [ 69.261648] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN [ 69.261650] RIP: 0010:idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261677] ? __warn (kernel/panic.c:242 kernel/panic.c:748) [69.261682] ? idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261687] ? report_bug (lib/bug.c:?) [ 69.261690] ? handle_bug (arch/x86/kernel/traps.c:285) [ 69.261694] ? exc_invalid_op (arch/x86/kernel/traps.c:309) [ 69.261697] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [69.261700] ? __pfx_idpf_vport_splitq_napi_poll (drivers/net/ethernet/intel/idpf/idpf_txrx.c:4011) idpf [69.261704] ? idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261708] ? idpf_vport_splitq_napi_poll (drivers/net/ethernet/intel/idpf/idpf_txrx.c:3072) idpf [ 69.261712]
    __napi_poll (net/core/dev.c:7194) [ 69.261716] net_rx_action (net/core/dev.c:7265) [ 69.261718] ?
    __qdisc_run (net/sched/sch_generic.c:293) [ 69.261721] ? sched_clock (arch/x86/include/asm/preempt.h:84 arch/x86/kernel/tsc.c:288) [ 69.261726] handle_softirqs (kernel/softirq.c:561) (CVE-2025-21890)

  - 已解決 Linux 核心中的下列弱點：idpf: check error for register_netdev() on init Current init logic ignores the error code from register_netdev(), which will cause WARN_ON() on attempt to unregister it, if there was one, and there is no info for the user that the creation of the netdev failed. WARNING: CPU: 89 PID: 6902 at net/core/dev.c:11512 unregister_netdevice_many_notify+0x211/0x1a10 ... [ 3707.563641] unregister_netdev+0x1c/0x30 [3707.563656] idpf_vport_dealloc+0x5cf/0xce0 [idpf] [ 3707.563684] idpf_deinit_task+0xef/0x160 [idpf] [3707.563712] idpf_vc_core_deinit+0x84/0x320 [idpf] [ 3707.563739] idpf_remove+0xbf/0x780 [idpf] [3707.563769] pci_device_remove+0xab/0x1e0 [ 3707.563786] device_release_driver_internal+0x371/0x530 [3707.563803] driver_detach+0xbf/0x180 [ 3707.563816] bus_remove_driver+0x11b/0x2a0 [ 3707.563829] pci_unregister_driver+0x2a/0x250 Introduce an error check and log the vport number and error code. On removal make sure to check VPORT_REG_NETDEV flag prior to calling unregister and free on the netdev. Add local variables for idx, vport_config and netdev for readability. (CVE-2025-22116)

  - 已解決 Linux 核心中的下列弱點：idpf: fix null-ptr-deref in idpf_features_check idpf_features_check is used to validate the TX packet. skb header length is compared with the hardware supported value received from the device control plane. The value is stored in the adapter structure and to access it, vport pointer is used. During reset all the vports are released and the vport pointer that the netdev private structure points to is NULL. To avoid null-ptr-deref, store the max header length value in netdev private structure. This also helps to cache the value and avoid accessing adapter pointer in hot path. BUG: kernel NULL pointer dereference, address: 0000000000000068 ...
    RIP: 0010:idpf_features_check+0x6d/0xe0 [idpf] Call Trace: <TASK> ? __die+0x23/0x70 ? page_fault_oops+0x154/0x520 ? exc_page_fault+0x76/0x190 ? asm_exc_page_fault+0x26/0x30 ? idpf_features_check+0x6d/0xe0 [idpf] netif_skb_features+0x88/0x310 validate_xmit_skb+0x2a/0x2b0 validate_xmit_skb_list+0x4c/0x70 sch_direct_xmit+0x19d/0x3a0 __dev_queue_xmit+0xb74/0xe70 ...
    (CVE-2025-38053)

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

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

    核心套件中包含 Linux 核心，後者是任何 Linux 作業系統的核心。

    安全性修正：

    * 核心: media: uvcvideo: 移除懸置指標 (CVE-2024-58002)

    * 核心：padata：修正 padata_reorder 中的 UAF (CVE-2025-21727)

    * 核心：media：uvcvideo：修復錯誤路徑中的重複釋放 (CVE-2024-57980)

    * 核心：HID：intel-ish-hid：修正 ishtp_hid_remove() 中的釋放後使用問題 (CVE-2025-21928)

    * 核心：sched/fair：修正 child_cfs_rq_on_list 中可能的記憶體損毀問題 (CVE-2025-21919)

    * 核心：ext4：修正 do_split 中的差一錯誤 (CVE-2025-23150)

    * 核心：misc/vmw_vmci：修復 vmci_host_do_receive_datagram() 中的資訊洩漏 (CVE-2022-49788)

    * 核心：net/tipc：修正 tipc_aead_encrypt_done 中的 slab-use-after-free 讀取 (CVE-2025-38052)

    * 核心：ext4：避免調整為部分叢集大小 (CVE-2022-50020)

    * 核心driversmd修正一個潛在的釋放後使用錯誤 (CVE-2022-50022)

    * 核心：net：ch9200：修復 mii_nway_restart 期間的未初始化存取 (CVE-2025-38086)

    * 核心i2c/designware修正初始化問題 (CVE-2025-38380)

    如需安全問題的詳細資料，包括影響、CVSS 分數、致謝及其他相關資訊，請參閱〈參照〉一節列出的 CVE 頁面。

Tenable 已直接從 Red Hat Enterprise Linux 安全公告擷取前置描述區塊。

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

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

  - i2c/designware修复一个初始化问题 i2c_dw_xfer_init() 函数需要要初始化的 dev 上下文中的 msgs 和 msg_write_idx。 amd_i2c_dw_xfer_quirk() 初始化 msgs 和 msgs_num但不初始化 msg_write_idx。这可允许消息的越界访问。调用 i2c_dw_xfer_init() 之前初始化 msg_write_idx。 (CVE-2025-38380)

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

远程 CentOS Linux 9 主机上存在安装的程序包该程序包受到 kernel-5.14.0-604.el9 版本变更日志中提及的多个漏洞的影响。

  - 已修复 Linux 内核中的下列漏洞：idpf: fix adapter NULL pointer dereference on reboot With SRIOV enabled, idpf ends up calling into idpf_remove() twice. First via idpf_shutdown() and then again when idpf_remove() calls into sriov_disable(), because the VF devices use the idpf driver, hence the same remove routine. When that happens, it is possible for the adapter to be NULL from the first call to idpf_remove(), leading to a NULL pointer dereference. echo 1 > /sys/class/net/<netif>/device/sriov_numvfs reboot BUG: kernel NULL pointer dereference, address:
    0000000000000020 ... RIP: 0010:idpf_remove+0x22/0x1f0 [idpf] ... ? idpf_remove+0x22/0x1f0 [idpf] ? idpf_remove+0x1e4/0x1f0 [idpf] pci_device_remove+0x3f/0xb0 device_release_driver_internal+0x19f/0x200 pci_stop_bus_device+0x6d/0x90 pci_stop_and_remove_bus_device+0x12/0x20 pci_iov_remove_virtfn+0xbe/0x120 sriov_disable+0x34/0xe0 idpf_sriov_configure+0x58/0x140 [idpf] idpf_remove+0x1b9/0x1f0 [idpf] idpf_shutdown+0x12/0x30 [idpf] pci_device_shutdown+0x35/0x60 device_shutdown+0x156/0x200 ... Replace the direct idpf_remove() call in idpf_shutdown() with idpf_vc_core_deinit() and idpf_deinit_dflt_mbx(), which perform the bulk of the cleanup, such as stopping the init task, freeing IRQs, destroying the vports and freeing the mailbox. This avoids the calls to sriov_disable() in addition to a small netdev cleanup, and destroying workqueues, which don't seem to be required on shutdown. (CVE-2025-22065)

  - 已修复 Linux 内核中的下列漏洞：idpf: convert workqueues to unbound When a workqueue is created with `WQ_UNBOUND`, its work items are served by special worker-pools, whose host workers are not bound to any specific CPU. In the default configuration (i.e. when `queue_delayed_work` and friends do not specify which CPU to run the work item on), `WQ_UNBOUND` allows the work item to be executed on any CPU in the same node of the CPU it was enqueued on. While this solution potentially sacrifices locality, it avoids contention with other processes that might dominate the CPU time of the processor the work item was scheduled on. This is not just a theoretical problem: in a particular scenario misconfigured process was hogging most of the time from CPU0, leaving less than 0.5% of its CPU time to the kworker. The IDPF workqueues that were using the kworker on CPU0 suffered large completion delays as a result, causing performance degradation, timeouts and eventual system crash. * I have also run a manual test to gauge the performance improvement. The test consists of an antagonist process (`./stress --cpu 2`) consuming as much of CPU 0 as possible. This process is run under `taskset 01` to bind it to CPU0, and its priority is changed with `chrt -pQ 9900 10000 ${pid}` and `renice -n -20 ${pid}` after start. Then, the IDPF driver is forced to prefer CPU0 by editing all calls to `queue_delayed_work`, `mod_delayed_work`, etc... to use CPU 0. Finally, `ktraces` for the workqueue events are collected. Without the current patch, the antagonist process can force arbitrary delays between `workqueue_queue_work` and `workqueue_execute_start`, that in my tests were as high as `30ms`. With the current patch applied, the workqueue can be migrated to another unloaded CPU in the same node, and, keeping everything else equal, the maximum delay I could see was `6us`. (CVE-2024-58057)

  - 已修复 Linux 内核中的下列漏洞：idpf: fix checksums set in idpf_rx_rsc() idpf_rx_rsc() uses skb_transport_offset(skb) while the transport header is not set yet. This triggers the following warning for CONFIG_DEBUG_NET=y builds.
    DEBUG_NET_WARN_ON_ONCE(!skb_transport_header_was_set(skb)) [ 69.261620] WARNING: CPU: 7 PID: 0 at ./include/linux/skbuff.h:3020 idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261629] Modules linked in: vfat fat dummy bridge intel_uncore_frequency_tpmi intel_uncore_frequency_common intel_vsec_tpmi idpf intel_vsec cdc_ncm cdc_eem cdc_ether usbnet mii xhci_pci xhci_hcd ehci_pci ehci_hcd libeth [ 69.261644] CPU: 7 UID: 0 PID: 0 Comm: swapper/7 Tainted: G S W 6.14.0-smp-DEV #1697 [ 69.261648] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN [ 69.261650] RIP: 0010:idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261677] ? __warn (kernel/panic.c:242 kernel/panic.c:748) [69.261682] ? idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261687] ? report_bug (lib/bug.c:?) [ 69.261690] ? handle_bug (arch/x86/kernel/traps.c:285) [ 69.261694] ? exc_invalid_op (arch/x86/kernel/traps.c:309) [ 69.261697] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [69.261700] ? __pfx_idpf_vport_splitq_napi_poll (drivers/net/ethernet/intel/idpf/idpf_txrx.c:4011) idpf [69.261704] ? idpf_vport_splitq_napi_poll (include/linux/skbuff.h:3020) idpf [ 69.261708] ? idpf_vport_splitq_napi_poll (drivers/net/ethernet/intel/idpf/idpf_txrx.c:3072) idpf [ 69.261712]
    __napi_poll (net/core/dev.c:7194) [ 69.261716] net_rx_action (net/core/dev.c:7265) [ 69.261718] ?
    __qdisc_run (net/sched/sch_generic.c:293) [ 69.261721] ? sched_clock (arch/x86/include/asm/preempt.h:84 arch/x86/kernel/tsc.c:288) [ 69.261726] handle_softirqs (kernel/softirq.c:561) (CVE-2025-21890)

  - 已修复 Linux 内核中的下列漏洞：idpf: check error for register_netdev() on init Current init logic ignores the error code from register_netdev(), which will cause WARN_ON() on attempt to unregister it, if there was one, and there is no info for the user that the creation of the netdev failed. WARNING: CPU: 89 PID: 6902 at net/core/dev.c:11512 unregister_netdevice_many_notify+0x211/0x1a10 ... [ 3707.563641] unregister_netdev+0x1c/0x30 [3707.563656] idpf_vport_dealloc+0x5cf/0xce0 [idpf] [ 3707.563684] idpf_deinit_task+0xef/0x160 [idpf] [3707.563712] idpf_vc_core_deinit+0x84/0x320 [idpf] [ 3707.563739] idpf_remove+0xbf/0x780 [idpf] [3707.563769] pci_device_remove+0xab/0x1e0 [ 3707.563786] device_release_driver_internal+0x371/0x530 [3707.563803] driver_detach+0xbf/0x180 [ 3707.563816] bus_remove_driver+0x11b/0x2a0 [ 3707.563829] pci_unregister_driver+0x2a/0x250 Introduce an error check and log the vport number and error code. On removal make sure to check VPORT_REG_NETDEV flag prior to calling unregister and free on the netdev. Add local variables for idx, vport_config and netdev for readability. (CVE-2025-22116)

  - 已修复 Linux 内核中的下列漏洞：idpf: fix null-ptr-deref in idpf_features_check idpf_features_check is used to validate the TX packet. skb header length is compared with the hardware supported value received from the device control plane. The value is stored in the adapter structure and to access it, vport pointer is used. During reset all the vports are released and the vport pointer that the netdev private structure points to is NULL. To avoid null-ptr-deref, store the max header length value in netdev private structure. This also helps to cache the value and avoid accessing adapter pointer in hot path. BUG: kernel NULL pointer dereference, address: 0000000000000068 ...
    RIP: 0010:idpf_features_check+0x6d/0xe0 [idpf] Call Trace: <TASK> ? __die+0x23/0x70 ? page_fault_oops+0x154/0x520 ? exc_page_fault+0x76/0x190 ? asm_exc_page_fault+0x26/0x30 ? idpf_features_check+0x6d/0xe0 [idpf] netif_skb_features+0x88/0x310 validate_xmit_skb+0x2a/0x2b0 validate_xmit_skb_list+0x4c/0x70 sch_direct_xmit+0x19d/0x3a0 __dev_queue_xmit+0xb74/0xe70 ...
    (CVE-2025-38053)

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

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

    内核程序包中包含 Linux 内核，后者是任何 Linux 操作系统的核心。

    安全修复：

    * kernel：media：uvcvideo：移除悬空指针 (CVE-2024-58002)

    * kernel: padata：修复 padata_reorder 中的 UAF (CVE-2025-21727)

    * kernel：media：uvcvideo：修复错误路径中的重复释放问题 (CVE-2024-57980)

    *kernel: HID : intel-ish-hid : 修复 ishtp_hid_remove() 中的释放后使用问题 (CVE-2025-21928)

    * 内核：sched/fair : 修复 child_cfs_rq_on_list 中潜在的内存损坏漏洞 (CVE-2025-21919)

    * 内核：ext4：修复 do_split 中的差一错误（CVE-2025-23150）

    * kernel：misc/vmw_vmci：修复 vmci_host_do_receive_datagram() 中的信息泄露问题 (CVE-2022-49788)

    * kernel: net/tipc：修复 tipc_aead_encrypt_done 中的 slab 释放后使用读取问题 (CVE-2025-38052)

    * kernel: ext4：避免调整为部分集群大小 (CVE-2022-50020)

    * kerneldrivers:md修复了潜在的释放后使用缺陷 (CVE-2022-50022)

    *kernel：net：ch9200：修复 mii_nway_restart 期间的未初始化访问 (CVE-2025-38086)

    * kerneli2c/designware修复一个初始化问题 (CVE-2025-38380)

    有关上述安全问题的更多详细信息，包括其影响、CVSS 得分、致谢，以及其他相关信息，请参阅列于“参考”部分的 CVE 页面。

Tenable 已直接从 Red Hat Enterprise Linux 安全公告中提取上述描述块。

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
249177	Debian dsa-5973affs-modules-6.1.0-37-4kc-malta-di - 安全更新	Nessus	Debian Local Security Checks	2025/8/13	2025/8/13	medium
245167	Linux Distros Unpatched Vulnerability : CVE-2025-38380	Nessus	Misc.	2025/8/7	2025/8/7	high
249174	CentOS 9 : kernel-5.14.0-604.el9	Nessus	CentOS Local Security Checks	2025/8/12	2025/8/12	medium
249209	RHEL 8 : kernel (RHSA-2025:13776)	Nessus	Red Hat Local Security Checks	2025/8/13	2025/8/13	high
249177	Debian dsa-5973 : affs-modules-6.1.0-37-4kc-malta-di - security update	Nessus	Debian Local Security Checks	2025/8/13	2025/8/13	medium
249174	CentOS 9kernel-5.14.0-604.el9	Nessus	CentOS Local Security Checks	2025/8/12	2025/8/12	medium
249209	RHEL 8：kernel（RHSA-2025:13776）	Nessus	Red Hat Local Security Checks	2025/8/13	2025/8/13	high
245167	Linux Distros のパッチ未適用の脆弱性: CVE-2025-38380	Nessus	Misc.	2025/8/7	2025/8/7	high
249177	Debian dsa-5973affs-modules-6.1.0-37-4kc-malta-di - 安全性更新	Nessus	Debian Local Security Checks	2025/8/13	2025/8/13	medium
249177	Debian dsa-5973 : affs-modules-6.1.0-37-4kc-malta-di - セキュリティ更新	Nessus	Debian Local Security Checks	2025/8/13	2025/8/13	medium
245167	Linux Distros 未修補的弱點：CVE-2025-38380	Nessus	Misc.	2025/8/7	2025/8/7	high
249174	CentOS 9kernel-5.14.0-604.el9	Nessus	CentOS Local Security Checks	2025/8/12	2025/8/12	medium
249209	RHEL 8：核心 (RHSA-2025:13776)	Nessus	Red Hat Local Security Checks	2025/8/13	2025/8/13	high
245167	Linux Distros 未修补的漏洞：CVE-2025-38380	Nessus	Misc.	2025/8/7	2025/8/7	high
249174	CentOS 9kernel-5.14.0-604.el9	Nessus	CentOS Local Security Checks	2025/8/12	2025/8/12	medium
249209	RHEL 8：内核 (RHSA-2025:13776)	Nessus	Red Hat Local Security Checks	2025/8/13	2025/8/13	high

检测

插件搜索

medium

high

medium

high

medium

medium

high

high

medium

medium

high

medium

high

high

medium

high