CVE-2022-49501: usbnet: Run unregister_netdev() before unbind() again
In the Linux kernel, the following vulnerability has been resolved:
usbnet: Run unregister_netdev() before unbind() again
Commit 2c9d6c2b871d ("usbnet: run unbind() before unregister_netdev()")
sought to fix a use-after-free on disconnect of USB Ethernet adapters.
It turns out that a different fix is necessary to address the issue:
https://lore.kernel.org/netdev/18b3541e5372bc9b9fc733d422f4e698c089077c.1650177997.git.lukas@wunner.de/
So the commit was not necessary.
The commit made binding and unbinding of USB Ethernet asymmetrical:
Before, usbnet_probe() first invoked the ->bind() callback and then
register_netdev(). usbnet_disconnect() mirrored that by first invoking
unregister_netdev() and then ->unbind().
Since the commit, the order in usbnet_disconnect() is reversed and no
longer mirrors usbnet_probe().
One consequence is that a PHY disconnected (and stopped) in ->unbind()
is afterwards stopped once more by unregister_netdev() as it closes the
netdev before unregistering. That necessitates a contortion in ->stop()
because the PHY may only be stopped if it hasn't already been
disconnected.
Reverting the commit allows making the call to phy_stop() unconditional
in ->stop().
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects USB Ethernet handling. A previous change altered disconnect order and could contribute to unsafe use-after-free behavior. The risk is local rather than internet-facing, but the CVSS score is high because successful exploitation could affect confidentiality, integrity, and availability.
Executive priority
Treat as high-priority for Linux fleets with local-user risk or USB Ethernet use. It is not presented as internet-exploited in the supplied evidence, so prioritize after remotely exploitable or KEV-listed issues unless local exposure is significant.
Technical view
The usbnet disconnect path must unregister the network device before driver unbind, matching probe order. The vulnerable ordering can leave teardown state inconsistent around PHY stop/disconnect handling. Sources identify CWE-416 and local, low-complexity, low-privilege impact with high CIA impact.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions or downstream builds that include the vulnerable usbnet change, especially where USB Ethernet adapters are used. Pure remote network exposure is not supported by the supplied sources.
Exploitation context
The bundle does not show CISA KEV listing or cited active exploitation. CVSS indicates local access with low privileges and no user interaction. Evidence supports serious local impact, not remote unauthenticated exploitation.
Researcher notes
The affected-version data is limited and partly commit-based. Validate against distro backports rather than only upstream version numbers. The core condition is usbnet teardown ordering around unregister_netdev, unbind, and PHY stop handling.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Check Linux distribution advisories for backported usbnet fixes.
Prioritize systems using USB Ethernet adapters or exposed to untrusted local users.
If patching is delayed, reduce untrusted local access to affected systems.
Validation and detection
Inventory kernel versions against vendor advisories and listed fixed commits.
Identify systems using usbnet-based USB Ethernet adapters.
Confirm downstream kernels include the stable fix or equivalent backport.
Review endpoint exposure to untrusted local users or device access.
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.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.