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

  - 已修复 Linux 内核中的下列漏洞：rtc: class: Fix potential memleak in devm_rtc_allocate_device() devm_rtc_allocate_device() will alloc a rtc_device first, and then run dev_set_name(). If dev_set_name() failed, the rtc_device will memleak. Move devm_add_action_or_reset() in front of dev_set_name() to prevent memleak. unreferenced object 0xffff888110a53000 (size 2048): comm python3, pid 470, jiffies 4296078308 (age 58.882s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 08 30 a5 10 81 88 ff ff .........0...... 08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00 .0..............
    backtrace: [<000000004aac0364>] kmalloc_trace+0x21/0x110 [<000000000ff02202>] devm_rtc_allocate_device+0xd4/0x400 [<000000001bdf5639>] devm_rtc_device_register+0x1a/0x80 [<00000000351bf81c>] rx4581_probe+0xdd/0x110 [rtc_rx4581] [<00000000f0eba0ae>] spi_probe+0xde/0x130 [<00000000bff89ee8>] really_probe+0x175/0x3f0 [<00000000128e8d84>] __driver_probe_device+0xe6/0x170 [<00000000ee5bf913>] device_driver_attach+0x32/0x80 [<00000000f3f28f92>] bind_store+0x10b/0x1a0 [<000000009ff812d8>] drv_attr_store+0x49/0x70 [<000000008139c323>] sysfs_kf_write+0x8d/0xb0 [<00000000b6146e01>] kernfs_fop_write_iter+0x214/0x2d0 [<00000000ecbe3895>] vfs_write+0x61a/0x7d0 [<00000000aa2196ea>] ksys_write+0xc8/0x190 [<0000000046a600f5>] do_syscall_64+0x37/0x90 [<00000000541a336f>] entry_SYSCALL_64_after_hwframe+0x63/0xcd (CVE-2022-50477)

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

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

  - 已解決 Linux 核心中的下列弱點：rtc: class: Fix potential memleak in devm_rtc_allocate_device() devm_rtc_allocate_device() will alloc a rtc_device first, and then run dev_set_name(). If dev_set_name() failed, the rtc_device will memleak. Move devm_add_action_or_reset() in front of dev_set_name() to prevent memleak. unreferenced object 0xffff888110a53000 (size 2048): comm python3, pid 470, jiffies 4296078308 (age 58.882s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 08 30 a5 10 81 88 ff ff .........0...... 08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00 .0..............
    backtrace: [<000000004aac0364>] kmalloc_trace+0x21/0x110 [<000000000ff02202>] devm_rtc_allocate_device+0xd4/0x400 [<000000001bdf5639>] devm_rtc_device_register+0x1a/0x80 [<00000000351bf81c>] rx4581_probe+0xdd/0x110 [rtc_rx4581] [<00000000f0eba0ae>] spi_probe+0xde/0x130 [<00000000bff89ee8>] really_probe+0x175/0x3f0 [<00000000128e8d84>] __driver_probe_device+0xe6/0x170 [<00000000ee5bf913>] device_driver_attach+0x32/0x80 [<00000000f3f28f92>] bind_store+0x10b/0x1a0 [<000000009ff812d8>] drv_attr_store+0x49/0x70 [<000000008139c323>] sysfs_kf_write+0x8d/0xb0 [<00000000b6146e01>] kernfs_fop_write_iter+0x214/0x2d0 [<00000000ecbe3895>] vfs_write+0x61a/0x7d0 [<00000000aa2196ea>] ksys_write+0xc8/0x190 [<0000000046a600f5>] do_syscall_64+0x37/0x90 [<00000000541a336f>] entry_SYSCALL_64_after_hwframe+0x63/0xcd (CVE-2022-50477)

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

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

  - Linux カーネルでは、以下の脆弱性が解決されています: rtc: class: Fix potential memleak in devm_rtc_allocate_device() devm_rtc_allocate_device() will alloc a rtc_device first, and then run dev_set_name(). If dev_set_name() failed, the rtc_device will memleak. Move devm_add_action_or_reset() in front of dev_set_name() to prevent memleak. unreferenced object 0xffff888110a53000 (size 2048): comm python3, pid 470, jiffies 4296078308 (age 58.882s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 08 30 a5 10 81 88 ff ff .........0...... 08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00 .0..............
    backtrace: [<000000004aac0364>] kmalloc_trace+0x21/0x110 [<000000000ff02202>] devm_rtc_allocate_device+0xd4/0x400 [<000000001bdf5639>] devm_rtc_device_register+0x1a/0x80 [<00000000351bf81c>] rx4581_probe+0xdd/0x110 [rtc_rx4581] [<00000000f0eba0ae>] spi_probe+0xde/0x130 [<00000000bff89ee8>] really_probe+0x175/0x3f0 [<00000000128e8d84>] __driver_probe_device+0xe6/0x170 [<00000000ee5bf913>] device_driver_attach+0x32/0x80 [<00000000f3f28f92>] bind_store+0x10b/0x1a0 [<000000009ff812d8>] drv_attr_store+0x49/0x70 [<000000008139c323>] sysfs_kf_write+0x8d/0xb0 [<00000000b6146e01>] kernfs_fop_write_iter+0x214/0x2d0 [<00000000ecbe3895>] vfs_write+0x61a/0x7d0 [<00000000aa2196ea>] ksys_write+0xc8/0x190 [<0000000046a600f5>] do_syscall_64+0x37/0x90 [<00000000541a336f>] entry_SYSCALL_64_after_hwframe+0x63/0xcd (CVE-2022-50477)

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

The AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1783355084 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: hwmon: (w83792d) Fix NULL pointer     dereference by removing unnecessary structure field If driver read val value sufficient for (val & 0x08)     && (!(val & 0x80)) && ((val & 0x7) == ((val >> 4) & 0x7)) from device then Null pointer dereference     occurs. (It is possible if tmp = 0b0xyz1xyz, where same literals mean same numbers) Also lm75[] does not     serve a purpose anymore after switching to devm_i2c_new_dummy_device() in w83791d_detect_subclients(). The     patch fixes possible NULL pointer dereference by removing lm75[]. Found by Linux Driver Verification     project (linuxtesting.org). [groeck: Dropped unnecessary continuation lines, fixed multipline alignment]     (CVE-2021-47385)

  - In the Linux kernel, the following vulnerability has been resolved: hwmon: (w83791d) Fix NULL pointer     dereference by removing unnecessary structure field If driver read val value sufficient for (val & 0x08)     && (!(val & 0x80)) && ((val & 0x7) == ((val >> 4) & 0x7)) from device then Null pointer dereference     occurs. (It is possible if tmp = 0b0xyz1xyz, where same literals mean same numbers) Also lm75[] does not     serve a purpose anymore after switching to devm_i2c_new_dummy_device() in w83791d_detect_subclients(). The     patch fixes possible NULL pointer dereference by removing lm75[]. Found by Linux Driver Verification     project (linuxtesting.org). [groeck: Dropped unnecessary continuation lines, fixed multi-line alignment]     (CVE-2021-47386)

  - In the Linux kernel, the following vulnerability has been resolved: mm/uffd: fix pte marker when fork()     without fork event Patch series mm: Fixes on pte markers. Patch 1 resolves the syzkiller report from     Pengfei. Patch 2 further harden pte markers when used with the recent swapin error markers. The major case     is we should persist a swapin error marker after fork(), so child shouldn't read a corrupted page. This     patch (of 2): When fork(), dst_vma is not guaranteed to have VM_UFFD_WP even if src may have it and has     pte marker installed. The warning is improper along with the comment. The right thing is to inherit the     pte marker when needed, or keep the dst pte empty. A vague guess is this happened by an accident when     there's the prior patch to introduce src/dst vma into this helper during the uffd-wp feature got developed     and I probably messed up in the rebase, since if we replace dst_vma with src_vma the warning & comment it     all makes sense too. Hugetlb did exactly the right here (copy_hugetlb_page_range()). Fix the general path.
    Reproducer: https://github.com/xupengfe/syzkaller_logs/blob/main/221208_115556_copy_page_range/repro.c     Bugzilla report: https://bugzilla.kernel.org/show_bug.cgi?id=216808 (CVE-2022-49744)

  - In the Linux kernel, the following vulnerability has been resolved: drm/vkms: Fix memory leak in     vkms_init() A memory leak was reported after the vkms module install failed. unreferenced object     0xffff88810bc28520 (size 16): comm modprobe, pid 9662, jiffies 4298009455 (age 42.590s) hex dump (first     16 bytes): 01 01 00 64 81 88 ff ff 00 00 dc 0a 81 88 ff ff ...d............ backtrace:
    [<00000000e7561ff8>] kmalloc_trace+0x27/0x60 [<000000000b1954a0>] 0xffffffffc45200a9 [<00000000abbf1da0>]     do_one_initcall+0xd0/0x4f0 [<000000001505ee87>] do_init_module+0x1a4/0x680 [<00000000958079ad>]     load_module+0x6249/0x7110 [<00000000117e4696>] __do_sys_finit_module+0x140/0x200 [<00000000f74b12d2>]     do_syscall_64+0x35/0x80 [<000000008fc6fcde>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 The reason is that     the vkms_init() returns without checking the return value of vkms_create(), and if the vkms_create()     failed, the config allocated at the beginning of vkms_init() is leaked. vkms_init() config = kmalloc(...)     # config allocated ... return vkms_create() # vkms_create failed and config is leaked Fix this problem by     checking return value of vkms_create() and free the config if error happened. (CVE-2022-50269)

  - In the Linux kernel, the following vulnerability has been resolved: net: hns: fix possible memory leak in     hnae_ae_register() Inject fault while probing module, if device_register() fails, but the refcount of     kobject is not decreased to 0, the name allocated in dev_set_name() is leaked. Fix this by calling     put_device(), so that name can be freed in callback function kobject_cleanup(). unreferenced object     0xffff00c01aba2100 (size 128): comm systemd-udevd, pid 1259, jiffies 4294903284 (age 294.152s) hex dump     (first 32 bytes): 68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff hnae0....!...... 00 00 00 00 00 00 00 00     00 00 00 00 00 00 00 00 ................ backtrace: [<0000000034783f26>] slab_post_alloc_hook+0xa0/0x3e0     [<00000000748188f2>] __kmem_cache_alloc_node+0x164/0x2b0 [<00000000ab0743e8>]
    __kmalloc_node_track_caller+0x6c/0x390 [<000000006c0ffb13>] kvasprintf+0x8c/0x118 [<00000000fa27bfe1>]     kvasprintf_const+0x60/0xc8 [<0000000083e10ed7>] kobject_set_name_vargs+0x3c/0xc0 [<000000000b87affc>]     dev_set_name+0x7c/0xa0 [<000000003fd8fe26>] hnae_ae_register+0xcc/0x190 [hnae] [<00000000fe97edc9>]     hns_dsaf_ae_init+0x9c/0x108 [hns_dsaf] [<00000000c36ff1eb>] hns_dsaf_probe+0x548/0x748 [hns_dsaf]     (CVE-2022-50352)

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

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

  - In the Linux kernel, the following vulnerability has been resolved: rtc: class: Fix potential memleak in     devm_rtc_allocate_device() devm_rtc_allocate_device() will alloc a rtc_device first, and then run     dev_set_name(). If dev_set_name() failed, the rtc_device will memleak. Move devm_add_action_or_reset() in     front of dev_set_name() to prevent memleak. unreferenced object 0xffff888110a53000 (size 2048): comm     python3, pid 470, jiffies 4296078308 (age 58.882s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 08     30 a5 10 81 88 ff ff .........0...... 08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00 .0..............
    backtrace: [<000000004aac0364>] kmalloc_trace+0x21/0x110 [<000000000ff02202>]     devm_rtc_allocate_device+0xd4/0x400 [<000000001bdf5639>] devm_rtc_device_register+0x1a/0x80     [<00000000351bf81c>] rx4581_probe+0xdd/0x110 [rtc_rx4581] [<00000000f0eba0ae>] spi_probe+0xde/0x130     [<00000000bff89ee8>] really_probe+0x175/0x3f0 [<00000000128e8d84>] __driver_probe_device+0xe6/0x170     [<00000000ee5bf913>] device_driver_attach+0x32/0x80 [<00000000f3f28f92>] bind_store+0x10b/0x1a0     [<000000009ff812d8>] drv_attr_store+0x49/0x70 [<000000008139c323>] sysfs_kf_write+0x8d/0xb0     [<00000000b6146e01>] kernfs_fop_write_iter+0x214/0x2d0 [<00000000ecbe3895>] vfs_write+0x61a/0x7d0     [<00000000aa2196ea>] ksys_write+0xc8/0x190 [<0000000046a600f5>] do_syscall_64+0x37/0x90     [<00000000541a336f>] entry_SYSCALL_64_after_hwframe+0x63/0xcd (CVE-2022-50477)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
269375	Linux Distros 未修补的漏洞：CVE-2022-50477	Nessus	Misc.	2025/10/8	2026/7/25	medium
269375	Linux Distros 未修補的弱點：CVE-2022-50477	Nessus	Misc.	2025/10/8	2026/7/25	medium
269375	Linux Distros のパッチ未適用の脆弱性: CVE-2022-50477	Nessus	Misc.	2025/10/8	2026/7/25	medium
361044	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1783355084)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/1	medium
269375	Linux Distros Unpatched Vulnerability : CVE-2022-50477	Nessus	Misc.	2025/10/8	2026/7/25	medium

检测

插件搜索

medium

medium

medium

medium

medium