CVE-2022-50476
published 2025-10-04CVE-2022-50476: In the Linux kernel, the following vulnerability has been resolved: ntb_netdev: Use dev_kfree_skb_any() in interrupt context TX/RX callback handlers…
PriorityP422medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.15%
4.6th percentile
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
23 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.4-1 (bookworm) | linux 6.1.4-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 548c237c0a9972df5d1afaca38aa733ee577128d < d4460c82177899751975180c268f352893302221 | d4460c82177899751975180c268f352893302221 |
| linux | linux | >= 548c237c0a9972df5d1afaca38aa733ee577128d < dd860b39aa7c7b82e6c99b6fdb99d4610ce49d67 | dd860b39aa7c7b82e6c99b6fdb99d4610ce49d67 |
| linux | linux | >= 548c237c0a9972df5d1afaca38aa733ee577128d < 8b78493968ed3cef0326183ed059c55e42f24d5b | 8b78493968ed3cef0326183ed059c55e42f24d5b |
| linux | linux | >= 548c237c0a9972df5d1afaca38aa733ee577128d < a6b9e09403102bdf8402dae734800e4916c7ea58 | a6b9e09403102bdf8402dae734800e4916c7ea58 |
| linux | linux | >= 548c237c0a9972df5d1afaca38aa733ee577128d < 13286ad1c7c49c606fdcba4cf66f953a1a16c1ca | 13286ad1c7c49c606fdcba4cf66f953a1a16c1ca |
| linux | linux | >= 548c237c0a9972df5d1afaca38aa733ee577128d < 21296a52caa6a6bad6debdfe40ad81d4f1a27e69 | 21296a52caa6a6bad6debdfe40ad81d4f1a27e69 |
| linux | linux | >= 548c237c0a9972df5d1afaca38aa733ee577128d < 14d245da57a11e80277ab455aa9b6dcc5ed38a19 | 14d245da57a11e80277ab455aa9b6dcc5ed38a19 |
| linux | linux | >= 548c237c0a9972df5d1afaca38aa733ee577128d < 07e28a8f450217db679802ebd4de0915556ce846 | 07e28a8f450217db679802ebd4de0915556ce846 |
| linux | linux | >= 548c237c0a9972df5d1afaca38aa733ee577128d < 5f7d78b2b12a9d561f48fa00bab29b40f4616dad | 5f7d78b2b12a9d561f48fa00bab29b40f4616dad |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 3.9 < 4.9.337 | 4.9.337 |
| linux | linux_kernel | >= 4.10 < 4.14.303 | 4.14.303 |
| linux | linux_kernel | >= 4.15 < 4.19.270 | 4.19.270 |
| linux | linux_kernel | >= 4.20 < 5.4.229 | 5.4.229 |
| linux | linux_kernel | >= 5.11 < 5.15.86 | 5.15.86 |
| linux | linux_kernel | >= 5.16 < 6.0.16 | 6.0.16 |
| linux | linux_kernel | >= 5.5 < 5.10.163 | 5.10.163 |
| linux | linux_kernel | >= 6.1 < 6.1.2 | 6.1.2 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2022-50476: In the Linux kernel, the following vulnerability has been resolved: ntb_netdev: Use dev_kfree_skb_any() in interrupt context TX/RX callback handlers (
osv·2025-10-04·CVSS 5.5
CVE-2022-50476 [MEDIUM] CVE-2022-50476: In the Linux kernel, the following vulnerability has been resolved: ntb_netdev: Use dev_kfree_skb_any() in interrupt context TX/RX callback handlers (
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
GHSA
GHSA-gh9q-398w-69gx: In the Linux kernel, the following vulnerability has been resolved:
ntb_netdev: Use dev_kfree_skb_any() in interrupt context
TX/RX callback handlers
ghsa_unreviewed·2025-10-04
CVE-2022-50476 [MEDIUM] CWE-401 GHSA-gh9q-398w-69gx: In the Linux kernel, the following vulnerability has been resolved:
ntb_netdev: Use dev_kfree_skb_any() in interrupt context
TX/RX callback handlers
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
Red Hat
kernel: ntb_netdev: Use dev_kfree_skb_any() in interrupt context
vendor_redhat·2025-10-04·CVSS 5.5
CVE-2022-50476 [MEDIUM] CWE-763 kernel: ntb_netdev: Use dev_kfree_skb_any() in interrupt context
kernel: ntb_netdev: Use dev_kfree_skb_any() in interrupt context
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
encoun
Debian
CVE-2022-50476: linux - In the Linux kernel, the following vulnerability has been resolved: ntb_netdev:...
vendor_debian·2022·CVSS 5.5
CVE-2022-50476 [MEDIUM] CVE-2022-50476: linux - In the Linux kernel, the following vulnerability has been resolved: ntb_netdev:...
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
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/07e28a8f450217db679802ebd4de0915556ce846https://git.kernel.org/stable/c/13286ad1c7c49c606fdcba4cf66f953a1a16c1cahttps://git.kernel.org/stable/c/14d245da57a11e80277ab455aa9b6dcc5ed38a19https://git.kernel.org/stable/c/21296a52caa6a6bad6debdfe40ad81d4f1a27e69https://git.kernel.org/stable/c/5f7d78b2b12a9d561f48fa00bab29b40f4616dadhttps://git.kernel.org/stable/c/8b78493968ed3cef0326183ed059c55e42f24d5bhttps://git.kernel.org/stable/c/a6b9e09403102bdf8402dae734800e4916c7ea58https://git.kernel.org/stable/c/d4460c82177899751975180c268f352893302221https://git.kernel.org/stable/c/dd860b39aa7c7b82e6c99b6fdb99d4610ce49d67
2025-10-04
Published