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

  - ntb_netdev在中断上下文中使用 dev_kfree_skb_any()当各自的 DMA 操作完成时可通过 DMA 框架在中断上下文中调用 TX/RX 回调处理程序ntb_netdev_tx_handler()、ntb_netdev_rx_handler()。因此这些例程对释放 skb 的调用都应使用中断上下文安全的 dev_kfree_skb_any() 函数。以前这些回调处理程序会调用中断 不安全的 dev_kfree_skb() 版本。这并未在 Intel IOAT DMA 引擎上出现问题因为该驱动程序利用 tasklet 而非硬中断处理程序如 AMD PTDMA DMA 驱动程序。在 AMD 系统上遇到内核“警告”消息由于 in_hardirq() 为 true该消息从 skb_release_head_state() 发出。除了用户可见的来自内核的“警告”之外此缺陷的其他征兆还包括通过 ntb_netdev 接口的 TCP/IP 性能非常差即比预期低一个数量级左右。通过修复以使用 dev_kfree_skb_any()来自 skb_release_head_state() 的内核警告停止并且由 iperf 测量的 TCP/IP 性能与预期结果相当在基于 AMDMilan 的服务器上大约为 20 Gb/s。请注意此性能与基于 Intel 的服务器具有可比性。 (CVE-2022-50476)

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

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

  - ntb_netdev在中斷內容中使用 dev_kfree_skb_any()當個別 DMA 作業完成時可以在中斷內容中透過 DMA 架構呼叫 TX/RX 回呼處置程式 (ntb_netdev_tx_handler()、ntb_netdev_rx_handler())。因此這些常式發出的任何呼叫釋放 skb 都應使用中斷內容安全的 dev_kfree_skb_any() 函式。之前這些回呼處置程式會呼叫 dev_kfree_skb() 的中斷不安全版本。這並未在 Intel IOAT DMA 引擎上出現問題因為該驅動程式使用 tasklet而非硬中斷處置程式 (例如 AMD PTDMA DMA 驅動程式)。在 AMD 系統上遇到核心警告訊息由於 in_hardirq() 為 true因此該訊息是從 skb_release_head_state() 發出。除了核心中使用者可見警告此錯誤的另一個徵兆是整個 ntb_netdev 介面的 TCP/IP 效能非常差即比預期低大約一個數量級。在使用 dev_kfree_skb_any() 進行修復之後skb_release_head_state() 的核心警告會停止且 TCP/IP 效能 (以 iperf 衡量) 與預期結果相當在 AMD Milan 型伺服器上約為 20 Gb/s。請注意此效能可與 Intel 型伺服器相提並論。 (CVE-2022-50476)

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

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

  - ntb_netdev割り込みコンテキストで dev_kfree_skb_any() を使用します。ntb_netdev_tx_handler()、ntb_netdev_rx_handler()は、それぞれの DMA 操作が完了したときに、DMA フレームワークを介して、割り込みコンテキストで呼び出すことができます。そのため、これらのルーチンによる skb を解放する呼び出しは、割り込みコンテキストセーフの dev_kfree_skb_any() 関数を使用する必要があります。以前は、これらのコールバックハンドラーは dev_kfree_skb() の割り込みの安全でないバージョンを呼び出していました。これは、AMD PTDMA DMA ドライバーなどのハード割り込みハンドラーではなく、ドライバーがタスクレットを利用するため、Intel IOAT DMA エンジンでは問題ありません。AMD システムで、カーネル警告メッセージが発生します。これは、in_hardirq() が true であるため、skb_release_head_state() から発行されます。カーネルからのユーザーに見える警告に加えて、このバグの他の兆候は、ntb_netdev インターフェイス全体で TCP/IP パフォーマンスが非常に貧弱であり、つまり、予想よりも桁違いに低いものでした。dev_kfree_skb_any() を使用するための修正では、skb_release_head_state() からのカーネル WARNING が停止し、iperf で測定された TCP/IP パフォーマンスは、AMD Milan ベースのサーバーで約 20 Gb/s の想定される結果と同等になりました。このパフォーマンスは Intel ベースのサーバーに同等です。CVE-2022-50476

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

An update of the linux package has been released.

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

  - ntb_netdev: Use dev_kfree_skb_any() in interrupt context TX/RX callback handlers (ntb_netdev_tx_handler(),     ntb_netdev_rx_handler()) can be called in interrupt context via the DMA framework when the respective DMA     operations have completed. As such, any calls by these routines to free skb's, should use the interrupt     context safe dev_kfree_skb_any() function. Previously, these callback handlers would call the interrupt     unsafe version of dev_kfree_skb(). This has not presented an issue on Intel IOAT DMA engines as that     driver utilizes tasklets rather than a hard interrupt handler, like the AMD PTDMA DMA driver. On AMD     systems, a kernel WARNING message is encountered, which is being issued from skb_release_head_state() due     to in_hardirq() being true. Besides the user visible WARNING from the kernel, the other symptom of this     bug was that TCP/IP performance across the ntb_netdev interface was very poor, i.e. approximately an order     of magnitude below what was expected. With the repair to use dev_kfree_skb_any(), kernel WARNINGs from     skb_release_head_state() ceased and TCP/IP performance, as measured by iperf, was on par with expected     results, approximately 20 Gb/s on AMD Milan based server. Note that this performance is comparable with     Intel based servers. (CVE-2022-50476)

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-005730 advisory.

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

    ntb_netdev: Use dev_kfree_skb_any() in interrupt context

    TX/RX callback handlers (ntb_netdev_tx_handler(),     ntb_netdev_rx_handler()) can be called in interrupt     context via the DMA framework when the respective     DMA operations have completed. As such, any calls     by these routines to free skb's, should use the     interrupt context safe dev_kfree_skb_any() function.

    Previously, these callback handlers would call the     interrupt unsafe version of dev_kfree_skb(). This has     not presented an issue on Intel IOAT DMA engines as     that driver utilizes tasklets rather than a hard     interrupt handler, like the AMD PTDMA DMA driver.
    On AMD systems, a kernel WARNING message is     encountered, which is being issued from     skb_release_head_state() due to in_hardirq()     being true.

    Besides the user visible WARNING from the kernel,     the other symptom of this bug was that TCP/IP performance     across the ntb_netdev interface was very poor, i.e.
    approximately an order of magnitude below what was     expected. With the repair to use dev_kfree_skb_any(),     kernel WARNINGs from skb_release_head_state() ceased     and TCP/IP performance, as measured by iperf, was on     par with expected results, approximately 20 Gb/s on     AMD Milan based server. Note that this performance     is comparable with Intel based servers.

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 Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-011028 advisory.

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

    ntb_netdev: Use dev_kfree_skb_any() in interrupt context

    TX/RX callback handlers (ntb_netdev_tx_handler(),     ntb_netdev_rx_handler()) can be called in interrupt     context via the DMA framework when the respective     DMA operations have completed. As such, any calls     by these routines to free skb's, should use the     interrupt context safe dev_kfree_skb_any() function.

    Previously, these callback handlers would call the     interrupt unsafe version of dev_kfree_skb(). This has     not presented an issue on Intel IOAT DMA engines as     that driver utilizes tasklets rather than a hard     interrupt handler, like the AMD PTDMA DMA driver.
    On AMD systems, a kernel WARNING message is     encountered, which is being issued from     skb_release_head_state() due to in_hardirq()     being true.

    Besides the user visible WARNING from the kernel,     the other symptom of this bug was that TCP/IP performance     across the ntb_netdev interface was very poor, i.e.
    approximately an order of magnitude below what was     expected. With the repair to use dev_kfree_skb_any(),     kernel WARNINGs from skb_release_head_state() ceased     and TCP/IP performance, as measured by iperf, was on     par with expected results, approximately 20 Gb/s on     AMD Milan based server. Note that this performance     is comparable with Intel based servers.

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 Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-006950 advisory.

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

    ntb_netdev: Use dev_kfree_skb_any() in interrupt context

    TX/RX callback handlers (ntb_netdev_tx_handler(),     ntb_netdev_rx_handler()) can be called in interrupt     context via the DMA framework when the respective     DMA operations have completed. As such, any calls     by these routines to free skb's, should use the     interrupt context safe dev_kfree_skb_any() function.

    Previously, these callback handlers would call the     interrupt unsafe version of dev_kfree_skb(). This has     not presented an issue on Intel IOAT DMA engines as     that driver utilizes tasklets rather than a hard     interrupt handler, like the AMD PTDMA DMA driver.
    On AMD systems, a kernel WARNING message is     encountered, which is being issued from     skb_release_head_state() due to in_hardirq()     being true.

    Besides the user visible WARNING from the kernel,     the other symptom of this bug was that TCP/IP performance     across the ntb_netdev interface was very poor, i.e.
    approximately an order of magnitude below what was     expected. With the repair to use dev_kfree_skb_any(),     kernel WARNINGs from skb_release_head_state() ceased     and TCP/IP performance, as measured by iperf, was on     par with expected results, approximately 20 Gb/s on     AMD Milan based server. Note that this performance     is comparable with Intel based servers.

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	名称	产品	系列	发布时间	最近更新时间	严重程度
269391	Linux Distros 未修补的漏洞：CVE-2022-50476	Nessus	Misc.	2025/10/8	2026/1/14	high
269391	Linux Distros 未修補的弱點：CVE-2022-50476	Nessus	Misc.	2025/10/8	2026/1/14	high
269391	Linux Distros のパッチ未適用の脆弱性: CVE-2022-50476	Nessus	Misc.	2025/10/8	2026/1/14	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	2021/7/22	2026/3/23	high
269391	Linux Distros Unpatched Vulnerability : CVE-2022-50476	Nessus	Misc.	2025/10/8	2026/1/14	high
300888	Unity Linux 20.1070a Security Update: kernel (UTSA-2026-005730)	Nessus	Unity Linux Local Security Checks	2026/3/5	2026/3/5	medium
308852	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-011028)	Nessus	Unity Linux Local Security Checks	2026/4/21	2026/4/21	medium
308276	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2026-006950)	Nessus	Unity Linux Local Security Checks	2026/4/21	2026/4/21	medium

检测

插件搜索

high

high

high

high

high

medium

medium

medium