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).
Security readout for executives and security teams
Plain-English summary
CVE-2025-22050 is a Linux kernel usbnet flaw that can crash a system. The issue is a race in USB networking receive handling that can lead to a NULL pointer dereference and kernel panic. The sources do not provide CVSS, exploitability prerequisites, or evidence of active exploitation.
Executive priority
Treat this as a patching priority for Linux assets that rely on USB networking or embedded/appliance use cases. It is not supported as an active exploitation emergency by the provided sources, but a kernel panic can cause service interruption.
Technical view
The usbnet receive path lacks a usbnet_going_away validation around usb_submit_urb, unlike __usbnet_queue_skb. A race can allow URB submission to succeed while the SKB is not queued, after which rx_complete/defer_bh processing may dereference skb->next and panic the kernel.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions with usbnet-based USB networking paths in use. The bundle lists affected Linux versions including 6.12, 5.15.180, 6.1.134, 6.6.87, 6.12.23, 6.13.11, 6.14.2, and 6.15.
Exploitation context
The bundle does not show active exploitation, KEV listing, public exploit code, or remote attack details. Based on the description, the confirmed impact is availability loss through kernel panic. Trigger conditions and attacker positioning are not fully evidenced in the provided sources.
Researcher notes
Evidence supports a kernel availability bug in usbnet receive completion. Public details name the faulty race and stable commits, but not a CVSS vector, CWE, exploit status, or detailed prerequisites. Validation should focus on affected kernel lineage and distro backports.
Mitigation direction
Apply Linux stable kernel updates containing the referenced usbnet fixes.
Use Debian LTS kernel updates where Debian LTS systems are affected.
Check distribution or vendor advisories for exact fixed package versions.
Prioritize systems using USB network adapters or usbnet-dependent deployments.
If patching is delayed, seek vendor guidance for temporary exposure reduction.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and endpoints.
Identify systems using usbnet or USB network adapter functionality.
Compare running kernels with vendor fixed versions and stable commit backports.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve ยท low confidence lookup
CVE-2025-22050 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
1ADP providers
9Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Apr 16, 2025, 14:12 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.