Linux Kernel up to 6.0.2 usb idmouse_open uninitialized pointer

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.0.2. This vulnerability affects the function idmouse_open of the component usb. Performing a manipulation results in uninitialized pointer. This vulnerability is cataloged as CVE-2022-50733. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.0.2. This affects the function idmouse_open of the component usb. The manipulation with an unknown input leads to a uninitialized pointer vulnerability. CWE is classifying the issue as CWE-824. The product accesses or uses a pointer that has not been initialized. This is going to have an impact on availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-50733 since 12/24/2025. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 279923 (Linux Distros Unpatched Vulnerability : CVE-2022-50733), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17 or 6.0.3 eliminates this vulnerability. Applying the patch b3304a6df957cc89a0590cb505388d659bf3db4c/7dad42032f68718259590b0cc7654e9a95ff9762/f589b667567fde4f81d6e6c40f42b9f2224690ea/1eae30c0113dde7522088231584d62415011a035/b8bbae3236ab7dccc66c42bc3f7cdbcfc0786e54/20b8c456df584ebb2387dc23d40ebe4ff334417c/6163a5ae097bc78fa26c243fb384537e25610fd7/adad163d1cff248a5df9f7cec50158e6ca89f33b/bce2b0539933e485d22d6f6f076c0fcd6f185c4c is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (279923) and CERT Bund (WID-SEC-2025-2929). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Uninitialized pointer
CWE: CWE-824 / CWE-908
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 279923
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2022-50733

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.9.331/4.14.296/4.19.262/5.4.220/5.10.150/5.15.75/5.19.17/6.0.3
Patch: b3304a6df957cc89a0590cb505388d659bf3db4c/7dad42032f68718259590b0cc7654e9a95ff9762/f589b667567fde4f81d6e6c40f42b9f2224690ea/1eae30c0113dde7522088231584d62415011a035/b8bbae3236ab7dccc66c42bc3f7cdbcfc0786e54/20b8c456df584ebb2387dc23d40ebe4ff334417c/6163a5ae097bc78fa26c243fb384537e25610fd7/adad163d1cff248a5df9f7cec50158e6ca89f33b/bce2b0539933e485d22d6f6f076c0fcd6f185c4c

Timelineinfo

12/24/2025 Advisory disclosed
12/24/2025 +0 days CVE reserved
12/24/2025 +0 days VulDB entry created
04/21/2026 +118 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-50733 (🔒)
GCVE (CVE): GCVE-0-2022-50733
GCVE (VulDB): GCVE-100-337989
CERT Bund: WID-SEC-2025-2929 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 12/24/2025 14:29
Updated: 04/21/2026 02:35
Changes: 12/24/2025 14:29 (59), 12/26/2025 11:43 (2), 12/29/2025 16:16 (7), 04/21/2026 02:35 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!