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

  - hwrnggeode - 修正由 pci_get_device() 實作的 PCI 裝置 refcount 洩漏 (for_each_pci_dev())。pci_get_device() 的註解指出其會增加已傳回之 pci_dev 的參照計數同時也會減少輸入 pci_dev @from (若不是 NULL) 的參照計數。如果我們在 pdev 不是 NULL 的情況下中斷 for_each_pci_dev() 迴圈則需要呼叫 pci_dev_put() 以減少參照計數。
    我們新增結構「amd_geode_priv」以記錄 pci_dev 和 membase 的指標然後針對正常和錯誤路徑新增缺少的 pci_dev_put()。 (CVE-2022-50659)

請注意，Nessus 的判定取決於廠商所報告的套件是否存在。

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

  - hwrnggeode - 修复由 pci_get_device() 实现的 for_each_pci_dev() 的 PCI 设备引用计数泄漏。pci_get_device() 的注释称其将会增加返回的 pci_dev 的引用计数同时会减少输入 pci_dev @from 的引用计数如果其不为 NULL。如果中断 pdev 不为 NULL 的 for_each_pci_dev() 循环则需要调用 pci_dev_put() 以减少引用计数。
    我们添加了一个新的 struct“amd_geode_priv”以记录 pci_dev 和 membase 的指针然后为正常和错误路径添加缺少的 pci_dev_put()。 (CVE-2022-50659)

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

如 TuxCare CENTOS6：CLSA-2026：1792975902公告所述，CentOS Linux 6 主机上安装有受到多个漏洞影响的程序包。

  - 已修复 Linux 内核中的下列漏洞：hwrng: geode - Fix PCI device refcount leak for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL. If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. We add a new struct 'amd_geode_priv' to record pointer of the pci_dev and membase, and then add missing pci_dev_put() for the normal and error path.
    (CVE-2022-50659)

  - 已修复 Linux 内核中的下列漏洞：ubi: Fix use-after-free when volume resizing failed There is an use-after-free problem reported by KASAN:
    ================================================================== BUG: KASAN: use-after-free in ubi_eba_copy_table+0x11f/0x1c0 [ubi] Read of size 8 at addr ffff888101eec008 by task ubirsvol/4735 CPU: 2 PID: 4735 Comm: ubirsvol Not tainted 6.1.0-rc1-00003-g84fa3304a7fc-dirty #14 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 print_report+0x171/0x472 kasan_report+0xad/0x130 ubi_eba_copy_table+0x11f/0x1c0 [ubi] ubi_resize_volume+0x4f9/0xbc0 [ubi] ubi_cdev_ioctl+0x701/0x1850 [ubi] __x64_sys_ioctl+0x11d/0x170 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 </TASK> When ubi_change_vtbl_record() returns an error in ubi_resize_volume(), new_eba_tbl will be freed on error handing path, but it is holded by vol->eba_tbl in ubi_eba_replace_table(). It means that the liftcycle of vol->eba_tbl and vol are different, so when resizing volume in next time, it causing an use-after-free fault. Fix it by not freeing new_eba_tbl after it replaced in ubi_eba_replace_table(), while will be freed in next volume resizing. (CVE-2023-53800)

  - 已修复 Linux 内核中的下列漏洞：media: av7110: prevent underflow in write_ts_to_decoder() The buf[4] value comes from the user via ts_play(). It is a value in the u8 range.
    The final length we pass to av7110_ipack_instant_repack() is len - (buf[4] + 1) - 4 so add a check to ensure that the length is not negative. It's not clear that passing a negative len value does anything bad necessarily, but it's not best practice. With the new bounds checking the if (!len) condition is no longer possible or required so remove that. (CVE-2023-54284)

  - 已修复 Linux 内核中的下列漏洞：ext4: fix dirtyclusters double decrement on fs shutdown fstests test generic/388 occasionally reproduces a warning in ext4_put_super() associated with the dirty clusters count: WARNING: CPU: 7 PID: 76064 at fs/ext4/super.c:1324 ext4_put_super+0x48c/0x590 [ext4] Tracing the failure shows that the warning fires due to an s_dirtyclusters_counter value of -1. IOW, this appears to be a spurious decrement as opposed to some sort of leak. Further tracing of the dirty cluster count deltas and an LLM scan of the resulting output identified the cause as a double decrement in the error path between ext4_mb_mark_diskspace_used() and the caller ext4_mb_new_blocks(). First, note that generic/388 is a shutdown vs. fsstress test and so produces a random set of operations and shutdown injections. In the problematic case, the shutdown triggers an error return from the ext4_handle_dirty_metadata() call(s) made from ext4_mb_mark_context(). The changed value is non-zero at this point, so ext4_mb_mark_diskspace_used() does not exit after the error bubbles up from ext4_mb_mark_context(). Instead, the former decrements both cluster counters and returns the error up to ext4_mb_new_blocks(). The latter falls into the !ar->len out path which decrements the dirty clusters counter a second time, creating the inconsistency. To avoid this problem and simplify ownership of the cluster reservation in this codepath, lift the counter reduction to a single place in the caller. This makes it more clear that ext4_mb_new_blocks() is responsible for acquiring cluster reservation (via ext4_claim_free_clusters()) in the !delalloc case as well as releasing it, regardless of whether it ends up consumed or returned due to failure. (CVE-2026-45920)

  - 已修复 Linux 内核中的下列漏洞：wifi: b43: enforce bounds check on firmware key index in b43_rx() The firmware-controlled key index in b43_rx() can exceed the dev->key[] array size (58 entries). The existing B43_WARN_ON is non-enforcing in production builds, allowing an out-of-bounds read. Make the B43_WARN_ON check enforcing by dropping the frame when the firmware returns an invalid key index. (CVE-2026-46122)

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

CentOS Linux 6 主機安裝的套件會受到 TuxCare CENTOS6：CLSA-2026：1792975902 公告中提及的多個弱點影響。

  - 已解決 Linux 核心中的下列弱點：hwrng: geode - Fix PCI device refcount leak for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL. If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. We add a new struct 'amd_geode_priv' to record pointer of the pci_dev and membase, and then add missing pci_dev_put() for the normal and error path.
    (CVE-2022-50659)

  - 已解決 Linux 核心中的下列弱點：ubi: Fix use-after-free when volume resizing failed There is an use-after-free problem reported by KASAN:
    ================================================================== BUG: KASAN: use-after-free in ubi_eba_copy_table+0x11f/0x1c0 [ubi] Read of size 8 at addr ffff888101eec008 by task ubirsvol/4735 CPU: 2 PID: 4735 Comm: ubirsvol Not tainted 6.1.0-rc1-00003-g84fa3304a7fc-dirty #14 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 print_report+0x171/0x472 kasan_report+0xad/0x130 ubi_eba_copy_table+0x11f/0x1c0 [ubi] ubi_resize_volume+0x4f9/0xbc0 [ubi] ubi_cdev_ioctl+0x701/0x1850 [ubi] __x64_sys_ioctl+0x11d/0x170 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 </TASK> When ubi_change_vtbl_record() returns an error in ubi_resize_volume(), new_eba_tbl will be freed on error handing path, but it is holded by vol->eba_tbl in ubi_eba_replace_table(). It means that the liftcycle of vol->eba_tbl and vol are different, so when resizing volume in next time, it causing an use-after-free fault. Fix it by not freeing new_eba_tbl after it replaced in ubi_eba_replace_table(), while will be freed in next volume resizing. (CVE-2023-53800)

  - 已解決 Linux 核心中的下列弱點：media: av7110: prevent underflow in write_ts_to_decoder() The buf[4] value comes from the user via ts_play(). It is a value in the u8 range.
    The final length we pass to av7110_ipack_instant_repack() is len - (buf[4] + 1) - 4 so add a check to ensure that the length is not negative. It's not clear that passing a negative len value does anything bad necessarily, but it's not best practice. With the new bounds checking the if (!len) condition is no longer possible or required so remove that. (CVE-2023-54284)

  - 已解決 Linux 核心中的下列弱點：ext4: fix dirtyclusters double decrement on fs shutdown fstests test generic/388 occasionally reproduces a warning in ext4_put_super() associated with the dirty clusters count: WARNING: CPU: 7 PID: 76064 at fs/ext4/super.c:1324 ext4_put_super+0x48c/0x590 [ext4] Tracing the failure shows that the warning fires due to an s_dirtyclusters_counter value of -1. IOW, this appears to be a spurious decrement as opposed to some sort of leak. Further tracing of the dirty cluster count deltas and an LLM scan of the resulting output identified the cause as a double decrement in the error path between ext4_mb_mark_diskspace_used() and the caller ext4_mb_new_blocks(). First, note that generic/388 is a shutdown vs. fsstress test and so produces a random set of operations and shutdown injections. In the problematic case, the shutdown triggers an error return from the ext4_handle_dirty_metadata() call(s) made from ext4_mb_mark_context(). The changed value is non-zero at this point, so ext4_mb_mark_diskspace_used() does not exit after the error bubbles up from ext4_mb_mark_context(). Instead, the former decrements both cluster counters and returns the error up to ext4_mb_new_blocks(). The latter falls into the !ar->len out path which decrements the dirty clusters counter a second time, creating the inconsistency. To avoid this problem and simplify ownership of the cluster reservation in this codepath, lift the counter reduction to a single place in the caller. This makes it more clear that ext4_mb_new_blocks() is responsible for acquiring cluster reservation (via ext4_claim_free_clusters()) in the !delalloc case as well as releasing it, regardless of whether it ends up consumed or returned due to failure. (CVE-2026-45920)

  - 已解決 Linux 核心中的下列弱點：wifi: b43: enforce bounds check on firmware key index in b43_rx() The firmware-controlled key index in b43_rx() can exceed the dev->key[] array size (58 entries). The existing B43_WARN_ON is non-enforcing in production builds, allowing an out-of-bounds read. Make the B43_WARN_ON check enforcing by dropping the frame when the firmware returns an invalid key index. (CVE-2026-46122)

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

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

  - hwrnggeode - PCI デバイス refcount の漏洩を修正します for_each_pci_dev() は、pci_get_device() により実装されます。pci_get_device() のコメントは、返される pci_dev の参照カウントを増加させ、また NULL でない場合、入力 pci_dev @from の参照カウントを減少させることを報告しています。NULL ではない pdev で for_each_pci_dev() ループを中断する場合、pci_dev_put() を呼び出して参照カウントを減らす必要があります。
    新しい構造体「amd_geode_priv」を pci_dev および membase のレコードポインターに追加し、通常およびエラーパスに対して欠落している pci_dev_put() を追加します。CVE-2022-50659

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

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

  - Linux カーネルでは、以下の脆弱性が解決されています: hwrng: geode - Fix PCI device refcount leak for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL. If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. We add a new struct 'amd_geode_priv' to record pointer of the pci_dev and membase, and then add missing pci_dev_put() for the normal and error path.
    (CVE-2022-50659)

  - Linux カーネルでは、以下の脆弱性が解決されています: ubi: Fix use-after-free when volume resizing failed There is an use-after-free problem reported by KASAN:
    ================================================================== BUG: KASAN: use-after-free in ubi_eba_copy_table+0x11f/0x1c0 [ubi] Read of size 8 at addr ffff888101eec008 by task ubirsvol/4735 CPU: 2 PID: 4735 Comm: ubirsvol Not tainted 6.1.0-rc1-00003-g84fa3304a7fc-dirty #14 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 print_report+0x171/0x472 kasan_report+0xad/0x130 ubi_eba_copy_table+0x11f/0x1c0 [ubi] ubi_resize_volume+0x4f9/0xbc0 [ubi] ubi_cdev_ioctl+0x701/0x1850 [ubi] __x64_sys_ioctl+0x11d/0x170 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 </TASK> When ubi_change_vtbl_record() returns an error in ubi_resize_volume(), new_eba_tbl will be freed on error handing path, but it is holded by vol->eba_tbl in ubi_eba_replace_table(). It means that the liftcycle of vol->eba_tbl and vol are different, so when resizing volume in next time, it causing an use-after-free fault. Fix it by not freeing new_eba_tbl after it replaced in ubi_eba_replace_table(), while will be freed in next volume resizing. (CVE-2023-53800)

  - Linux カーネルでは、以下の脆弱性が解決されています: media: av7110: prevent underflow in write_ts_to_decoder() The buf[4] value comes from the user via ts_play(). It is a value in the u8 range.
    The final length we pass to av7110_ipack_instant_repack() is len - (buf[4] + 1) - 4 so add a check to ensure that the length is not negative. It's not clear that passing a negative len value does anything bad necessarily, but it's not best practice. With the new bounds checking the if (!len) condition is no longer possible or required so remove that. (CVE-2023-54284)

  - Linux カーネルでは、以下の脆弱性が解決されています: ext4: fix dirtyclusters double decrement on fs shutdown fstests test generic/388 occasionally reproduces a warning in ext4_put_super() associated with the dirty clusters count: WARNING: CPU: 7 PID: 76064 at fs/ext4/super.c:1324 ext4_put_super+0x48c/0x590 [ext4] Tracing the failure shows that the warning fires due to an s_dirtyclusters_counter value of -1. IOW, this appears to be a spurious decrement as opposed to some sort of leak. Further tracing of the dirty cluster count deltas and an LLM scan of the resulting output identified the cause as a double decrement in the error path between ext4_mb_mark_diskspace_used() and the caller ext4_mb_new_blocks(). First, note that generic/388 is a shutdown vs. fsstress test and so produces a random set of operations and shutdown injections. In the problematic case, the shutdown triggers an error return from the ext4_handle_dirty_metadata() call(s) made from ext4_mb_mark_context(). The changed value is non-zero at this point, so ext4_mb_mark_diskspace_used() does not exit after the error bubbles up from ext4_mb_mark_context(). Instead, the former decrements both cluster counters and returns the error up to ext4_mb_new_blocks(). The latter falls into the !ar->len out path which decrements the dirty clusters counter a second time, creating the inconsistency. To avoid this problem and simplify ownership of the cluster reservation in this codepath, lift the counter reduction to a single place in the caller. This makes it more clear that ext4_mb_new_blocks() is responsible for acquiring cluster reservation (via ext4_claim_free_clusters()) in the !delalloc case as well as releasing it, regardless of whether it ends up consumed or returned due to failure. (CVE-2026-45920)

  - Linux カーネルでは、以下の脆弱性が解決されています: wifi: b43: enforce bounds check on firmware key index in b43_rx() The firmware-controlled key index in b43_rx() can exceed the dev->key[] array size (58 entries). The existing B43_WARN_ON is non-enforcing in production builds, allowing an out-of-bounds read. Make the B43_WARN_ON check enforcing by dropping the frame when the firmware returns an invalid key index. (CVE-2026-46122)

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

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

  - hwrng: geode - Fix PCI device refcount leak for_each_pci_dev() is implemented by pci_get_device(). The     comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and     also decrease the reference count for the input pci_dev @from if it is not NULL. If we break     for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count.
    We add a new struct 'amd_geode_priv' to record pointer of the pci_dev and membase, and then add missing     pci_dev_put() for the normal and error path. (CVE-2022-50659)

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-010805 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    hwrng: geode - Fix PCI device refcount leak

    for_each_pci_dev() is implemented by pci_get_device(). The comment of     pci_get_device() says that it will increase the reference count for the     returned pci_dev and also decrease the reference count for the input     pci_dev @from if it is not NULL.

    If we break for_each_pci_dev() loop with pdev not NULL, we need to call     pci_dev_put() to decrease the reference count. We add a new struct     'amd_geode_priv' to record pointer of the pci_dev and membase, and then     add missing pci_dev_put() for the normal and error path.

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

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

An update of the linux package has been released.

The CentOS Linux 6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS6:CLSA-2026:1792975902 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: hwrng: geode - Fix PCI device refcount     leak for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it     will increase the reference count for the returned pci_dev and also decrease the reference count for the     input pci_dev @from if it is not NULL. If we break for_each_pci_dev() loop with pdev not NULL, we need to     call pci_dev_put() to decrease the reference count. We add a new struct 'amd_geode_priv' to record pointer     of the pci_dev and membase, and then add missing pci_dev_put() for the normal and error path.
    (CVE-2022-50659)

  - In the Linux kernel, the following vulnerability has been resolved: ubi: Fix use-after-free when volume     resizing failed There is an use-after-free problem reported by KASAN:
    ================================================================== BUG: KASAN: use-after-free in     ubi_eba_copy_table+0x11f/0x1c0 [ubi] Read of size 8 at addr ffff888101eec008 by task ubirsvol/4735 CPU: 2     PID: 4735 Comm: ubirsvol Not tainted 6.1.0-rc1-00003-g84fa3304a7fc-dirty #14 Hardware name: QEMU Standard     PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44     print_report+0x171/0x472 kasan_report+0xad/0x130 ubi_eba_copy_table+0x11f/0x1c0 [ubi]     ubi_resize_volume+0x4f9/0xbc0 [ubi] ubi_cdev_ioctl+0x701/0x1850 [ubi] __x64_sys_ioctl+0x11d/0x170     do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 </TASK> When ubi_change_vtbl_record()     returns an error in ubi_resize_volume(), new_eba_tbl will be freed on error handing path, but it is     holded by vol->eba_tbl in ubi_eba_replace_table(). It means that the liftcycle of vol->eba_tbl and     vol are different, so when resizing volume in next time, it causing an use-after-free fault. Fix it by     not freeing new_eba_tbl after it replaced in ubi_eba_replace_table(), while will be freed in next volume     resizing. (CVE-2023-53800)

  - In the Linux kernel, the following vulnerability has been resolved: media: av7110: prevent underflow in     write_ts_to_decoder() The buf[4] value comes from the user via ts_play(). It is a value in the u8 range.
    The final length we pass to av7110_ipack_instant_repack() is len - (buf[4] + 1) - 4 so add a check to     ensure that the length is not negative. It's not clear that passing a negative len value does anything bad     necessarily, but it's not best practice. With the new bounds checking the if (!len) condition is no     longer possible or required so remove that. (CVE-2023-54284)

  - In the Linux kernel, the following vulnerability has been resolved: ext4: fix dirtyclusters double     decrement on fs shutdown fstests test generic/388 occasionally reproduces a warning in ext4_put_super()     associated with the dirty clusters count: WARNING: CPU: 7 PID: 76064 at fs/ext4/super.c:1324     ext4_put_super+0x48c/0x590 [ext4] Tracing the failure shows that the warning fires due to an     s_dirtyclusters_counter value of -1. IOW, this appears to be a spurious decrement as opposed to some sort     of leak. Further tracing of the dirty cluster count deltas and an LLM scan of the resulting output     identified the cause as a double decrement in the error path between ext4_mb_mark_diskspace_used() and the     caller ext4_mb_new_blocks(). First, note that generic/388 is a shutdown vs. fsstress test and so produces     a random set of operations and shutdown injections. In the problematic case, the shutdown triggers an     error return from the ext4_handle_dirty_metadata() call(s) made from ext4_mb_mark_context(). The changed     value is non-zero at this point, so ext4_mb_mark_diskspace_used() does not exit after the error bubbles up     from ext4_mb_mark_context(). Instead, the former decrements both cluster counters and returns the error up     to ext4_mb_new_blocks(). The latter falls into the !ar->len out path which decrements the dirty clusters     counter a second time, creating the inconsistency. To avoid this problem and simplify ownership of the     cluster reservation in this codepath, lift the counter reduction to a single place in the caller. This     makes it more clear that ext4_mb_new_blocks() is responsible for acquiring cluster reservation (via     ext4_claim_free_clusters()) in the !delalloc case as well as releasing it, regardless of whether it ends     up consumed or returned due to failure. (CVE-2026-45920)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: b43: enforce bounds check on     firmware key index in b43_rx() The firmware-controlled key index in b43_rx() can exceed the dev->key[]     array size (58 entries). The existing B43_WARN_ON is non-enforcing in production builds, allowing an out-     of-bounds read. Make the B43_WARN_ON check enforcing by dropping the frame when the firmware returns an     invalid key index. (CVE-2026-46122)

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-013795 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    hwrng: geode - Fix PCI device refcount leak

    for_each_pci_dev() is implemented by pci_get_device(). The comment of     pci_get_device() says that it will increase the reference count for the     returned pci_dev and also decrease the reference count for the input     pci_dev @from if it is not NULL.

    If we break for_each_pci_dev() loop with pdev not NULL, we need to call     pci_dev_put() to decrease the reference count. We add a new struct     'amd_geode_priv' to record pointer of the pci_dev and membase, and then     add missing pci_dev_put() for the normal and error path.

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

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

ID	名稱	產品	系列	已發布	已更新	嚴重性
278317	Linux Distros 未修補的弱點：CVE-2022-50659	Nessus	Misc.	2025/12/11	2026/9/30	medium
278317	Linux Distros 未修补的漏洞：CVE-2022-50659	Nessus	Misc.	2025/12/11	2026/9/30	medium
373891	CentOS Linux 6 [TuxCare] 安全更新：kernel / kernel-abi-whitelists / kernel-debug / kernel-debug-devel / 等多个漏洞（CENTOS6：CLSA-2026：1792975902）	Nessus	CentOS Local Security Checks	2026/10/29	2026/10/29	high
373891	CentOS Linux 6 [TuxCare] 安全性更新：kernel / kernel-abi-whitelists / kernel-debug / kernel-debug-devel / etc 多個弱點（CENTOS6：CLSA-2026：1792975902）	Nessus	CentOS Local Security Checks	2026/10/29	2026/10/29	high
278317	Linux Distros のパッチ未適用の脆弱性: CVE-2022-50659	Nessus	Misc.	2025/12/11	2026/9/30	medium
373891	CentOS Linux 6 [TuxCare] セキュリティ更新プログラム:カーネル/kernel-abi-whitelists/kernel-debug/kernel-debug-devel/etcの複数の脆弱性(CENTOS6:CLSA-2026:1792975902)	Nessus	CentOS Local Security Checks	2026/10/29	2026/10/29	high
278317	Linux Distros Unpatched Vulnerability : CVE-2022-50659	Nessus	Misc.	2025/12/11	2026/9/30	medium
309025	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-010805)	Nessus	Unity Linux Local Security Checks	2026/4/21	2026/4/21	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	2021/7/22	2026/11/2	high
373891	CentOS Linux 6 [TuxCare] Security Update: kernel / kernel-abi-whitelists / kernel-debug / kernel-debug-devel / etc Multiple Vulnerabilities (CENTOS6:CLSA-2026:1792975902)	Nessus	CentOS Local Security Checks	2026/10/29	2026/10/29	high
309469	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2026-013795)	Nessus	Unity Linux Local Security Checks	2026/4/22	2026/4/26	medium

偵測

搜尋 Plugin

medium

medium

high

high

medium

high

medium

medium

high

high

medium