CVE-2022-49389: usb: usbip: fix a refcount leak in stub_probe()
In the Linux kernel, the following vulnerability has been resolved:
usb: usbip: fix a refcount leak in stub_probe()
usb_get_dev() is called in stub_device_alloc(). When stub_probe() fails
after that, usb_put_dev() needs to be called to release the reference.
Fix this by moving usb_put_dev() to sdev_free error path handling.
Find this by code review.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49389 is a Linux kernel USB/IP bug that can leak a device reference when stub_probe() fails. The practical concern is local availability impact, not data theft. Sources rate it medium severity with high availability impact, low attack complexity, and required local low privileges.
Executive priority
Handle through normal kernel patch management unless USB/IP is important in the environment. There is no cited active exploitation, but the availability impact justifies tracking to closure on affected Linux assets.
Technical view
The flaw is a reference-count leak in Linux usbip stub_probe(). usb_get_dev() is called during stub_device_alloc(), but an error path failed to call usb_put_dev(). Stable commits move usb_put_dev() into sdev_free error handling. The issue was found by code review.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions with reachable USB/IP stub code paths. The CVE record names Linux kernel version ranges but does not identify affected distributions, appliances, or cloud images. Validate against vendor kernel packages and the listed upstream stable fixes.
Exploitation context
The source bundle reports local attack vector, low complexity, low privileges, no user interaction, and no confidentiality or integrity impact. It is not in KEV, and no cited source reports active exploitation or public exploit activity.
Researcher notes
Evidence supports a narrow kernel error-path refcount leak with availability impact. The bundle does not provide exploit mechanics, affected distribution mapping, or workaround details. Research should focus on kernel version mapping, USB/IP configuration exposure, and whether vendor backports include the stable commits.
Mitigation direction
Update affected Linux kernels to vendor releases containing the listed upstream stable fixes.
Check Linux distribution advisories for package-specific fixed versions.
Prioritize systems using USB/IP or exposing USB device virtualization workflows.
If patch timing is unclear, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory Linux kernel versions across servers, workstations, and embedded systems.
Compare running kernels with vendor advisories and the upstream stable commit list.
Identify hosts where USB/IP functionality is enabled or operationally required.
Confirm updated hosts boot into the fixed kernel, not only install it.
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-2022-49389 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.
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.