Linux Kernel up to 6.0.2 staging initialization

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.4$0-$5k0.00

Summaryinfo

A vulnerability has been found in Linux Kernel up to 6.0.2 and classified as critical. Affected by this issue is some unknown functionality of the component staging. The manipulation leads to initialization. This vulnerability is uniquely identified as CVE-2022-50355. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.0.2. This issue affects an unknown part of the component staging. The manipulation with an unknown input leads to a initialization vulnerability. Using CWE to declare the problem leads to CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: staging: vt6655: fix some erroneous memory clean-up loops In some initialization functions of this driver, memory is allocated with 'i' acting as an index variable and increasing from 0. The commit in "Fixes" introduces some clean-up codes in case of allocation failure, which free memory in reverse order with 'i' decreasing to 0. However, there are some problems: - The case i=0 is left out. Thus memory is leaked. - In case memory allocation fails right from the start, the memory freeing loops will start with i=-1 and invalid memory locations will be accessed. One of these loops has been fixed in commit c8ff91535880 ("staging: vt6655: fix potential memory leak"). Fix the remaining erroneous loops.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2022-50355 since 09/17/2025. Neither technical details nor an exploit are publicly available.

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

Upgrading to version 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 637672a71f5016a40b0a6c0f3c8ad25eacedc8c3/88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0/95ac62e8545be2b0a8cae0beef7c682e2e470e48/f19e5b7df54590c831f350381963f25585c8f7d5/a9e9806d1c315bc50dce05479a079b9a104474b8/ed11b73c963292e7b49c0f37025c58ed3b7921d6/2a2db520e3ca5aafba7c211abfd397666c9b5f9d 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 (265486) and CERT Bund (WID-SEC-2025-2087). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • SUSE Linux
  • Oracle Linux
  • IBM QRadar SIEM
  • Open Source Linux Kernel
  • RESF Rocky Linux
  • Dell Secure Connect Gateway

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

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

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

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

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

Exploitinginfo

Class: Initialization
CWE: CWE-665
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 265486
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2022-50355

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.19.262/5.4.220/5.10.150/5.15.75/5.19.17/6.0.3
Patch: 637672a71f5016a40b0a6c0f3c8ad25eacedc8c3/88b9cc60f26e8a05d1ddbddf91b09ca2915f20e0/95ac62e8545be2b0a8cae0beef7c682e2e470e48/f19e5b7df54590c831f350381963f25585c8f7d5/a9e9806d1c315bc50dce05479a079b9a104474b8/ed11b73c963292e7b49c0f37025c58ed3b7921d6/2a2db520e3ca5aafba7c211abfd397666c9b5f9d

Timelineinfo

09/17/2025 Advisory disclosed
09/17/2025 +0 days CVE reserved
09/17/2025 +0 days VulDB entry created
12/23/2025 +97 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-50355 (🔒)
GCVE (CVE): GCVE-0-2022-50355
GCVE (VulDB): GCVE-100-324677
CERT Bund: WID-SEC-2025-2087 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 09/17/2025 17:37
Updated: 12/23/2025 10:18
Changes: 09/17/2025 17:37 (58), 09/22/2025 18:08 (2), 12/10/2025 18:20 (10), 12/23/2025 10:18 (7)
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.

Interested in the pricing of exploits?

See the underground prices here!