Answer in brief
CVE-2022-50476 records a Medium severity (CVSS 5.5) vulnerability in ntb_netdev: Use dev_kfree_skb_any() in interrupt context. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=548c237c0a9972df5d1afaca38aa733ee577128d <d4460c82177899751975180c268f352893302221 || >=548c237c0a9972df5d1afaca38aa733ee577128d <dd860b39aa7c7b82e6c99b6fdb99d4610ce49d67 || >=548c237c0a9972df5d1afaca38aa733ee577128d <8b78493968ed3cef0326183ed059c55e42f24d5b || >=548c237c0a9972df5d1afaca38aa733ee577128d <a6b9e09403102bdf8402dae734800e4916c7ea58 || >=548c237c0a9972df5d1afaca38aa733ee577128d <13286ad1c7c49c606fdcba4cf66f953a1a16c1ca || >=548c237c0a9972df5d1afaca38aa733ee577128d <21296a52caa6a6bad6debdfe40ad81d4f1a27e69 || >=548c237c0a9972df5d1afaca38aa733ee577128d <14d245da57a11e80277ab455aa9b6dcc5ed38a19 || >=548c237c0a9972df5d1afaca38aa733ee577128d <07e28a8f450217db679802ebd4de0915556ce846 || >=548c237c0a9972df5d1afaca38aa733ee577128d <5f7d78b2b12a9d561f48fa00bab29b40f4616dad | d4460c82177899751975180c268f352893302221, dd860b39aa7c7b82e6c99b6fdb99d4610ce49d67, 8b78493968ed3cef0326183ed059c55e42f24d5b, a6b9e09403102bdf8402dae734800e4916c7ea58, 13286ad1c7c49c606fdcba4cf66f953a1a16c1ca, 21296a52caa6a6bad6debdfe40ad81d4f1a27e69, 14d245da57a11e80277ab455aa9b6dcc5ed38a19, 07e28a8f450217db679802ebd4de0915556ce846, 5f7d78b2b12a9d561f48fa00bab29b40f4616dad |
| Linux/Linuxgeneric | 3.9 | Not reported |
Published upstream
Oct 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.