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

14 results

Back

CVE-2025-22050usbnet:fix NPE during rx_complete

Description

In the Linux kernel, the following vulnerability has been resolved: usbnet:fix NPE during rx_complete Missing usbnet_going_away Check in Critical Path. The usb_submit_urb function lacks a usbnet_going_away validation, whereas __usbnet_queue_skb includes this check. This inconsistency creates a race condition where: A URB request may succeed, but the corresponding SKB data fails to be queued. Subsequent processes: (e.g., rx_complete → defer_bh → __skb_unlink(skb, list)) attempt to access skb->next, triggering a NULL pointer dereference (Kernel Panic).

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 19 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-2025-22050, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (17 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 4.7.

Affected products

  • Linux · Linux

    • affected b80aacfea6e8d6ed6e430aa13922d6ccf044415a – < 95789c2f94fd29dce8759f9766baa333f749287c
    • affected 869caa8de8cb94514df704ccbe0b024fda4b9398 – < 0f10f83acfd619e13c64d6705908dfd792f19544
    • affected 1e44ee6cdd123d6cfe78b4a94e1572e23bbb58ce – < acacd48a37b52fc95f621765762c04152b58d642
    • affected 04e906839a053f092ef53f4fb2d610983412b904 – < d689645cd1594ea1d13cb0c404f8ad1011353e0e
    • affected 04e906839a053f092ef53f4fb2d610983412b904 – < 0c30988588b28393e3e8873d5654f910e86391ba
    • affected 04e906839a053f092ef53f4fb2d610983412b904 – < fd9ee3f0d6a53844f65efde581c91bbb0ff749ac
    • affected 04e906839a053f092ef53f4fb2d610983412b904 – < 51de3600093429e3b712e5f091d767babc5dd6df
    • affected ca124236cd14e61610f56df9a8f81376a1ffe660
    • affected 54671d731f4977fb3c0c26f2840655b5204e4437
    • affected 5.15.168 – < 5.15.180
    • affected 6.1.113 – < 6.1.134
    • affected 6.6.54 – < 6.6.87
    • affected 6.10.13 – < 6.11
    • affected 6.11.2 – < 6.12
  • Linux · Linux

    • affected 6.12
    • unaffected < 6.12
    • unaffected 5.15.180 – ≤ 5.15.*
    • unaffected 6.1.134 – ≤ 6.1.*
    • unaffected 6.6.87 – ≤ 6.6.*
    • unaffected 6.12.23 – ≤ 6.12.*
    • unaffected 6.13.11 – ≤ 6.13.*
    • unaffected 6.14.2 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .