Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50476

ntb_netdev: Use dev_kfree_skb_any() in interrupt context

Medium5.5EPSS 0.16%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-50476, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (8 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

Affected products

  • Linux · Linux

    • affected 548c237c0a9972df5d1afaca38aa733ee577128d – < d4460c82177899751975180c268f352893302221
    • affected 548c237c0a9972df5d1afaca38aa733ee577128d – < dd860b39aa7c7b82e6c99b6fdb99d4610ce49d67
    • affected 548c237c0a9972df5d1afaca38aa733ee577128d – < 8b78493968ed3cef0326183ed059c55e42f24d5b
    • affected 548c237c0a9972df5d1afaca38aa733ee577128d – < a6b9e09403102bdf8402dae734800e4916c7ea58
    • affected 548c237c0a9972df5d1afaca38aa733ee577128d – < 13286ad1c7c49c606fdcba4cf66f953a1a16c1ca
    • affected 548c237c0a9972df5d1afaca38aa733ee577128d – < 21296a52caa6a6bad6debdfe40ad81d4f1a27e69
    • affected 548c237c0a9972df5d1afaca38aa733ee577128d – < 14d245da57a11e80277ab455aa9b6dcc5ed38a19
    • affected 548c237c0a9972df5d1afaca38aa733ee577128d – < 07e28a8f450217db679802ebd4de0915556ce846
    • affected 548c237c0a9972df5d1afaca38aa733ee577128d – < 5f7d78b2b12a9d561f48fa00bab29b40f4616dad
  • Linux · Linux

    • affected 3.9
    • unaffected < 3.9
    • unaffected 4.9.337 – ≤ 4.9.*
    • unaffected 4.14.303 – ≤ 4.14.*
    • unaffected 4.19.270 – ≤ 4.19.*
    • unaffected 5.4.229 – ≤ 5.4.*
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.86 – ≤ 5.15.*
    • unaffected 6.0.16 – ≤ 6.0.*
    • unaffected 6.1.2 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References (9)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50476 badge
[![CVE-2022-50476](https://cveledger.app/badge/CVE-2022-50476.svg)](https://cveledger.app/cve/CVE-2022-50476)

Record last updated .