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.

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.

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

An update of the linux package has been released.

ID	Name	Product	Family	Severity
308852	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-011028)	Nessus	Unity Linux Local Security Checks	medium
308276	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2026-006950)	Nessus	Unity Linux Local Security Checks	medium
300888	Unity Linux 20.1070a Security Update: kernel (UTSA-2026-005730)	Nessus	Unity Linux Local Security Checks	medium
269391	Linux Distros Unpatched Vulnerability : CVE-2022-50476	Nessus	Misc.	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	high

Detections

Analytics

CVE-2022-50476

medium

Tenable Plugins

medium

medium

medium

high

high