{"id":"CVE-2022-50476","title":"ntb_netdev: Use dev_kfree_skb_any() in interrupt context","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nntb_netdev: Use dev_kfree_skb_any() in interrupt context\n\nTX/RX callback handlers (ntb_netdev_tx_handler(),\nntb_netdev_rx_handler()) can be called in interrupt\ncontext …","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < d4460c82177899751975180c268f352893302221","Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < dd860b39aa7c7b82e6c99b6fdb99d4610ce49d67","Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < 8b78493968ed3cef0326183ed059c55e42f24d5b","Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < a6b9e09403102bdf8402dae734800e4916c7ea58","Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < 13286ad1c7c49c606fdcba4cf66f953a1a16c1ca","Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < 21296a52caa6a6bad6debdfe40ad81d4f1a27e69","Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < 14d245da57a11e80277ab455aa9b6dcc5ed38a19","Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < 07e28a8f450217db679802ebd4de0915556ce846","Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < 5f7d78b2b12a9d561f48fa00bab29b40f4616dad","Linux 3.9"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-11-05T20:11:51.249499Z"},"published":"2025-10-04","updated":"2026-11-05","sourceUpdated":"2026-11-05T20:20:47.899Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2022-50476","references":[{"url":"https://git.kernel.org/stable/c/d4460c82177899751975180c268f352893302221"},{"url":"https://git.kernel.org/stable/c/dd860b39aa7c7b82e6c99b6fdb99d4610ce49d67"},{"url":"https://git.kernel.org/stable/c/8b78493968ed3cef0326183ed059c55e42f24d5b"},{"url":"https://git.kernel.org/stable/c/a6b9e09403102bdf8402dae734800e4916c7ea58"},{"url":"https://git.kernel.org/stable/c/13286ad1c7c49c606fdcba4cf66f953a1a16c1ca"},{"url":"https://git.kernel.org/stable/c/21296a52caa6a6bad6debdfe40ad81d4f1a27e69"},{"url":"https://git.kernel.org/stable/c/14d245da57a11e80277ab455aa9b6dcc5ed38a19"},{"url":"https://git.kernel.org/stable/c/07e28a8f450217db679802ebd4de0915556ce846"},{"url":"https://git.kernel.org/stable/c/5f7d78b2b12a9d561f48fa00bab29b40f4616dad"}],"tags":["cve.org"],"epss":0.00163,"epssPercentile":0.05538,"ingestedAt":"2026-11-05T22:38:31.740Z","slug":"CVE-2022-50476","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nntb_netdev: Use dev_kfree_skb_any() in interrupt context\n\nTX/RX callback handlers (ntb_netdev_tx_handler(),\nntb_netdev_rx_handler()) can be called in interrupt\ncontext via the DMA framework when the respective\nDMA operations have completed. As such, any calls\nby these routines to free skb's, should use the\ninterrupt context safe dev_kfree_skb_any() function.\n\nPreviously, these callback handlers would call the\ninterrupt unsafe version of dev_kfree_skb(). This has\nnot presented an issue on Intel IOAT DMA engines as\nthat driver utilizes tasklets rather than a hard\ninterrupt handler, like the AMD PTDMA DMA driver.\nOn AMD systems, a kernel WARNING message is\nencountered, which is being issued from\nskb_release_head_state() due to in_hardirq()\nbeing true.\n\nBesides the user visible WARNING from the kernel,\nthe other symptom of this bug was that TCP/IP performance\nacross the ntb_netdev interface was very poor, i.e.\napproximately an order of magnitude below what was\nexpected. With the repair to use dev_kfree_skb_any(),\nkernel WARNINGs from skb_release_head_state() ceased\nand TCP/IP performance, as measured by iperf, was on\npar with expected results, approximately 20 Gb/s on\nAMD Milan based server. Note that this performance\nis comparable with Intel based servers.\n\n## Affected\n\n- `Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < d4460c82177899751975180c268f352893302221`\n- `Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < dd860b39aa7c7b82e6c99b6fdb99d4610ce49d67`\n- `Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < 8b78493968ed3cef0326183ed059c55e42f24d5b`\n- `Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < a6b9e09403102bdf8402dae734800e4916c7ea58`\n- `Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < 13286ad1c7c49c606fdcba4cf66f953a1a16c1ca`\n- `Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < 21296a52caa6a6bad6debdfe40ad81d4f1a27e69`\n- `Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < 14d245da57a11e80277ab455aa9b6dcc5ed38a19`\n- `Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < 07e28a8f450217db679802ebd4de0915556ce846`\n- `Linux >= 548c237c0a9972df5d1afaca38aa733ee577128d < 5f7d78b2b12a9d561f48fa00bab29b40f4616dad`\n- `Linux 3.9`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}