CVE-2022-50476

published 4 Oct 2025 · updated 7 Nov 2026

ntb_netdev: Use dev_kfree_skb_any() in interrupt context

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4.9.337, Kernel 4.14.303, Kernel 4.19.270 and 14 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=3.9 <4.9.337, >=4.10 <4.14.303, >=4.15 <4.19.270, >=4.20 <5.4.229, >=5.11 <5.15.86, >=5.16 <6.0.16, >=5.5 <5.10.163, >=6.1 <6.1.2, >=548c237c0a9972df5d1afaca38aa733ee577128d <13286ad1c7c49c606fdcba4cf66f953a1a16c1ca, >=548c237c0a9972df5d1afaca38aa733ee577128d <14d245da57a11e80277ab455aa9b6dcc5ed38a19, >=548c237c0a9972df5d1afaca38aa733ee577128d <21296a52caa6a6bad6debdfe40ad81d4f1a27e69, >=548c237c0a9972df5d1afaca38aa733ee577128d <5f7d78b2b12a9d561f48fa00bab29b40f4616dad, >=548c237c0a9972df5d1afaca38aa733ee577128d <8b78493968ed3cef0326183ed059c55e42f24d5b, >=548c237c0a9972df5d1afaca38aa733ee577128d <a6b9e09403102bdf8402dae734800e4916c7ea58, >=548c237c0a9972df5d1afaca38aa733ee577128d <d4460c82177899751975180c268f352893302221, >=548c237c0a9972df5d1afaca38aa733ee577128d <dd860b39aa7c7b82e6c99b6fdb99d4610ce49d67, =3.9, >=548c237c0a9972df5d1afaca38aa733ee577128d <07e28a8f450217db679802ebd4de0915556ce8464.9.337, 4.14.303, 4.19.270, 5.4.229, 5.15.86, 6.0.16, 5.10.163, 6.1.2, 13286ad1c7c49c606fdcba4cf66f953a1a16c1ca, 14d245da57a11e80277ab455aa9b6dcc5ed38a19, 21296a52caa6a6bad6debdfe40ad81d4f1a27e69, 5f7d78b2b12a9d561f48fa00bab29b40f4616dad, 8b78493968ed3cef0326183ed059c55e42f24d5b, a6b9e09403102bdf8402dae734800e4916c7ea58, d4460c82177899751975180c268f352893302221, dd860b39aa7c7b82e6c99b6fdb99d4610ce49d67, 07e28a8f450217db679802ebd4de0915556ce846
linux-kernel: Kernel>=3.9.0 <4.9.337, >=4.10.0 <4.14.303, >=4.15.0 <4.19.270, >=4.20.0 <5.4.229, >=5.11.0 <5.15.86, >=5.16.0 <6.0.16, >=5.5.0 <5.10.163, >=6.1.0 <6.1.24.9.337, 4.14.303, 4.19.270, 5.4.229, 5.15.86, 6.0.16, 5.10.163, 6.1.2

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-50476 severity on Zeptric[![CVE-2022-50476](https://zeptric.io/badge/cve/CVE-2022-50476.svg)](https://zeptric.io/cve/CVE-2022-50476)