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

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

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

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

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

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

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

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

  - 在 Linux 核心中snd_hdac_regmap_sync() 函式的 sound/hda 裝置驅動程式中發現一個爭用情形。這可導致 null 指標解除參照問題，進而可能導致核心錯誤或拒絕服務問題。(CVE-2024-23196)

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

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

  - 在 snd_hdac_regmap_sync() 函数的 Linux 内核的 sound/hda 设备驱动程序中发现争用条件。这可导致空指针取消引用问题，进而可能导致内核错误或拒绝服务问题。(CVE-2024-23196)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  - snd_hdac_regmap_sync() 関数の Linux カーネルの sound/hda デバイスドライバーに競合状態が見つかりました。これにより、NULL ポインターデリファレンスの問題が発生し、カーネルパニックまたはサービス拒否問題が発生する可能性があります。(CVE-2024-23196)

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

An update of the linux package has been released.

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

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

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

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

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

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

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

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

    A race condition was found in the Linux kernel's sound/hda  device driver in snd_hdac_regmap_sync()     function. This can result in a null pointer dereference issue, possibly leading to a kernel panic or     denial of service issue.



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.

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

  - A race condition was found in the Linux kernel's sound/hda device driver in snd_hdac_regmap_sync()     function. This can result in a null pointer dereference issue, possibly leading to a kernel panic or     denial of service issue. (CVE-2024-23196)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
360826	AlmaLinux 9.2 [TuxCare] 安全性更新：bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc 多個弱點（ALMALINUX9.2：CLSA-2026：1781347338）	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/19	high
228037	Linux Distros 未修補的弱點：CVE-2024-23196	Nessus	Misc.	2025/3/5	2026/11/6	medium
228037	Linux Distros 未修补的漏洞：CVE-2024-23196	Nessus	Misc.	2025/3/5	2026/11/6	medium
360826	AlmaLinux 9.2 [TuxCare] セキュリティ更新プログラム:bpftool/kernel/kernel-64k/kernel-64k-core/kernel-64k-debug/etcの複数の脆弱性(ALMALINUX9.2:CLSA-2026:1781347338)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/19	high
360826	AlmaLinux 9.2 [TuxCare] 安全更新：bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / 等多个漏洞（ALMALINUX9.2：CLSA-2026：1781347338）	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/19	high
228037	Linux Distros のパッチ未適用の脆弱性: CVE-2024-23196	Nessus	Misc.	2025/3/5	2026/11/6	medium
204585	Photon OS 5.0: Linux PHSA-2023-5.0-0101	Nessus	PhotonOS Local Security Checks	2024/7/24	2026/10/13	high
360826	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1781347338)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/19	high
332299	Photon OS 5.0: Linux PHSA-2023-5.0-91-0101	Nessus	PhotonOS Local Security Checks	2026/8/5	2026/11/2	high
341464	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2024-002968)	Nessus	Unity Linux Local Security Checks	2026/8/29	2026/8/29	medium
228037	Linux Distros Unpatched Vulnerability : CVE-2024-23196	Nessus	Misc.	2025/3/5	2026/11/6	medium

检测

插件搜索

high

medium

medium

high

high

medium

high

high

high

medium

medium