LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50733: usb: idmouse: fix an uninit-value in idmouse_open

In the Linux kernel, the following vulnerability has been resolved: usb: idmouse: fix an uninit-value in idmouse_open In idmouse_create_image, if any ftip_command fails, it will go to the reset label. However, this leads to the data in bulk_in_buffer[HEADER..IMGSIZE] uninitialized. And the check for valid image incurs an uninitialized dereference. Fix this by moving the check before reset label since this check only be valid if the data after bulk_in_buffer[HEADER] has concrete data. Note that this is found by KMSAN, so only kernel compilation is tested.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50733 is a Linux kernel USB driver bug in idmouse. A failed device command can leave part of an input buffer uninitialized, then later code may read it. The public record does not provide CVSS, confirmed impact, or evidence of exploitation.

Executive priority

Treat as routine-to-moderate Linux kernel patching unless your environment allows broad untrusted USB device access. There is no sourced evidence of exploitation or severe impact, but affected kernels should still be updated through normal vulnerability management cycles.

Technical view

In idmouse_open/idmouse_create_image, failures from ftip_command jump to reset while bulk_in_buffer image data may remain uninitialized. A subsequent valid-image check can dereference uninitialized data. The stable fix reorders the check so it only runs when image data is concrete. The issue was found by KMSAN; only kernel compilation testing is noted.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions with the USB idmouse driver present or usable. Risk is higher where untrusted USB peripherals can be attached. The CVE record lists multiple affected kernel release lines and kernel stable fix commits.

Exploitation context

No active exploitation is indicated in the provided sources, and the CVE is not marked KEV. The available description does not state whether this causes crash, data exposure, or privilege impact. Because it is in a USB driver path, attacker proximity or device access may be relevant, but sources do not fully define prerequisites.

Researcher notes

Evidence is limited. The CVE record provides commit references and root cause, but no CVSS, CWE, exploitability analysis, or runtime test results beyond KMSAN discovery and compile testing. Further assessment should review the exact stable commits and downstream distribution backports.

Mitigation direction

  • Update affected Linux kernels to versions containing the referenced stable fixes.
  • Check distribution or kernel vendor advisories for backported patches.
  • Limit use of untrusted USB devices until patched, where operationally feasible.
  • Prioritize systems where USB peripheral access is exposed to users or visitors.

Validation and detection

  • Inventory Linux kernel versions across managed systems.
  • Check whether the idmouse USB driver is built, loadable, or in use.
  • Map installed kernels against vendor advisories and referenced stable commits.
  • Confirm patched kernels are deployed after maintenance.
  • Monitor vendor guidance for clarified impact or additional affected versions.
Prepared
Confidence
medium
Sources
11

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-50733 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
0Timeline events
0ADP providers
10Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4244f72436ab77c3c29a6447af81734ab3925d85, 4244f72436ab77c3c29a6447af81734ab3925d85, 4244f72436ab77c3c29a6447af81734ab3925d85, 4244f72436ab77c3c29a6447af81734ab3925d85, 4244f72436ab77c3c29a6447af81734ab3925d85, 4244f72436ab77c3c29a6447af81734ab3925d85, 4244f72436ab77c3c29a6447af81734ab3925d85, 4244f72436ab77c3c29a6447af81734ab3925d85, 4244f72436ab77c3c29a6447af81734ab3925d85unaffected
LinuxLinux2.6.13, 0, 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.