Skip to content
Noroxi
CVE-2022-50476· NVD / CVE Program· CNA Linux

ntb_netdev: Use dev_kfree_skb_any() in interrupt context

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 07e28a8f450217db679802ebd4de0915556ce846, 13286ad1c7c49c606fdcba4cf66f953a1a16c1ca, 14d245da57a11e80277ab455aa9b6dcc5ed38a19.

Low priority for now. Upgrade to Linux Linux 07e28a8f450217db679802ebd4de0915556ce846, 13286ad1c7c49c606fdcba4cf66f953a1a16c1ca, 14d245da57a11e80277ab455aa9b6dcc5ed38a19 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Oct 4, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-50476

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.9 and later · before 4.9.337
  • linux linux kernel4.10 and later · before 4.14.303
  • linux linux kernel4.15 and later · before 4.19.270
  • linux linux kernel4.20 and later · before 5.4.229
  • linux linux kernel5.5 and later · before 5.10.163
  • linux linux kernel5.11 and later · before 5.15.86
  • linux linux kernel5.16 and later · before 6.0.16
  • linux linux kernel6.1 and later · before 6.1.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.9affected
    • 548c237c0a9972df5d1afaca38aa733ee577128d and later · before d4460c82177899751975180c268f352893302221affected · git
    • 548c237c0a9972df5d1afaca38aa733ee577128d and later · before dd860b39aa7c7b82e6c99b6fdb99d4610ce49d67affected · git
    • 548c237c0a9972df5d1afaca38aa733ee577128d and later · before 8b78493968ed3cef0326183ed059c55e42f24d5baffected · git
    • 548c237c0a9972df5d1afaca38aa733ee577128d and later · before a6b9e09403102bdf8402dae734800e4916c7ea58affected · git
    • 548c237c0a9972df5d1afaca38aa733ee577128d and later · before 13286ad1c7c49c606fdcba4cf66f953a1a16c1caaffected · git
    • 548c237c0a9972df5d1afaca38aa733ee577128d and later · before 21296a52caa6a6bad6debdfe40ad81d4f1a27e69affected · git
    • 548c237c0a9972df5d1afaca38aa733ee577128d and later · before 14d245da57a11e80277ab455aa9b6dcc5ed38a19affected · git
    • 548c237c0a9972df5d1afaca38aa733ee577128d and later · before 07e28a8f450217db679802ebd4de0915556ce846affected · git
    • 548c237c0a9972df5d1afaca38aa733ee577128d and later · before 5f7d78b2b12a9d561f48fa00bab29b40f4616dadaffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.4-16.1.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-50474Oct 4, 2025 · macintosh: fix possible memory leak in macio_add_one_device()
    22Monitor
  • ← EarlierCVE-2022-50475Oct 4, 2025 · RDMA/core: Make sure "ib_port" is valid when access sysfs node
    22Monitor
  • Later →CVE-2022-50477Oct 4, 2025 · rtc: class: Fix potential memleak in devm_rtc_allocate_device()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux07e28a8f450217db679802ebd4de0915556ce846Vendor (CNA)
Linux Linux13286ad1c7c49c606fdcba4cf66f953a1a16c1caVendor (CNA)
Linux Linux14d245da57a11e80277ab455aa9b6dcc5ed38a19Vendor (CNA)
Linux Linux21296a52caa6a6bad6debdfe40ad81d4f1a27e69Vendor (CNA)
Linux Linux5f7d78b2b12a9d561f48fa00bab29b40f4616dadVendor (CNA)
Linux Linux8b78493968ed3cef0326183ed059c55e42f24d5bVendor (CNA)
Linux Linuxa6b9e09403102bdf8402dae734800e4916c7ea58Vendor (CNA)
Linux Linuxd4460c82177899751975180c268f352893302221Vendor (CNA)
Linux Linuxdd860b39aa7c7b82e6c99b6fdb99d4610ce49d67Vendor (CNA)
debian:linux6.1.4-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-401 · Missing Release of Memory after Effective Lifetime

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records