CVE-2022-49501

published 26 Feb 2025 · updated 11 May 2026

usbnet: Run unregister_netdev() before unbind() again

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6d5deb242874d924beccf7eb3cef04c1c3b0da79, Kernel 969a1b3ea3cb7d58a16fe12fd1b04bfc0ea40509, Kernel d1408f6b4dd78fb1b9e26bcf64477984e5f85409 and 1 more.

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().

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.14, >=2c9d6c2b871d5841ce26ede3e81fd37e2e33c42c <6d5deb242874d924beccf7eb3cef04c1c3b0da79, >=2c9d6c2b871d5841ce26ede3e81fd37e2e33c42c <969a1b3ea3cb7d58a16fe12fd1b04bfc0ea40509, >=2c9d6c2b871d5841ce26ede3e81fd37e2e33c42c <d1408f6b4dd78fb1b9e26bcf64477984e5f85409, >=2c9d6c2b871d5841ce26ede3e81fd37e2e33c42c <fbda837107f9bd4ec658d2aa88c6856dba606f066d5deb242874d924beccf7eb3cef04c1c3b0da79, 969a1b3ea3cb7d58a16fe12fd1b04bfc0ea40509, d1408f6b4dd78fb1b9e26bcf64477984e5f85409, fbda837107f9bd4ec658d2aa88c6856dba606f06

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-49501 severity on Zeptric[![CVE-2022-49501](https://zeptric.io/badge/cve/CVE-2022-49501.svg)](https://zeptric.io/cve/CVE-2022-49501)