Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-49501

usbnet: Run unregister_netdev() before unbind() again

High7.8EPSS 0.27%
Published
Updated
Reserved
Assigned by
Linux

Description

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

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 15 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-2022-49501, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.27% · top 81% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Weakness

Affected products

  • Linux · Linux

    • affected 2c9d6c2b871d5841ce26ede3e81fd37e2e33c42c – < 6d5deb242874d924beccf7eb3cef04c1c3b0da79
    • affected 2c9d6c2b871d5841ce26ede3e81fd37e2e33c42c – < fbda837107f9bd4ec658d2aa88c6856dba606f06
    • affected 2c9d6c2b871d5841ce26ede3e81fd37e2e33c42c – < 969a1b3ea3cb7d58a16fe12fd1b04bfc0ea40509
    • affected 2c9d6c2b871d5841ce26ede3e81fd37e2e33c42c – < d1408f6b4dd78fb1b9e26bcf64477984e5f85409
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.46 – ≤ 5.15.*
    • unaffected 5.17.14 – ≤ 5.17.*
    • unaffected 5.18.3 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References (4)

Sources

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

Badge for a README or a ticket

CVE-2022-49501 badge
[![CVE-2022-49501](https://trackcve.app/badge/CVE-2022-49501.svg)](https://trackcve.app/cve/CVE-2022-49501)

Record last updated .